Revert incorrect InstalledPackage field additions per PR review

- Remove id field: InstalledPackage uses packageId as @id primary key
- Remove updatedAt field: Not defined in Prisma schema
- Revert tenantId back to null: 'default' tenant may not exist
- Schema defines: packageId @id, tenantId?, installedAt, version, enabled, config?

Co-authored-by: johndoe6345789 <224850594+johndoe6345789@users.noreply.github.com>

dbal/development/src/core/entities/operations/system/package/index.ts

@@ -56,11 +56,9 @@ const assertValidId = (id: string) => {
 const withInstalledPackageDefaults = (data: CreatePackageInput): InstalledPackage => {
   const installedAt = data.installedAt ?? BigInt(Date.now())
   return {
-    id: data.packageId, // Use packageId as id
     packageId: data.packageId,
     tenantId: data.tenantId ?? null,
     installedAt,
-    updatedAt: installedAt, // Set updatedAt to installedAt initially
     version: data.version,
     enabled: data.enabled,
     config: data.config ?? null,

dbal/development/src/core/entities/package/crud/create-package.ts

@@ -15,11 +15,9 @@ export const createPackage = async (
 ): Promise<Result<InstalledPackage>> => {
   const installedAt = input.installedAt ?? BigInt(Date.now())
   const payload: InstalledPackage = {
-    id: input.packageId, // Use packageId as id
     packageId: input.packageId,
     tenantId: input.tenantId ?? null,
     installedAt,
-    updatedAt: installedAt, // Set updatedAt to installedAt initially
     version: input.version,
     enabled: input.enabled,
     config: input.config ?? null