refactor(xo): removed ignores

[mfranzke]

Proposed changes

we shouldn't ignore xo in general. xo is here to hurt our feelings. If it does, that's a good thing.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (fix on existing components or architectural decisions)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Further comments

[github-actions]

🔭🐙🐈 Test this branch here: https://db-ui.github.io/mono/review/refactor-removed-xo-ignores

[Copilot]

Pull Request Overview

This PR refactors the migration and configuration files by removing unnecessary ignore patterns and updating import statements and file headers. Key changes include:

• Removing directories from .xo-config ignores to enforce linting on migration and foundations code.
• Updating type assertions and file path imports to include proper extensions and shebang directives.
• Standardizing import usage (e.g., using node built-ins) and simplifying error handling in the fonts generation script.

Reviewed Changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
packages/migration/test//.spec.ts	Replaced explicit type cast with non-null assertion in test expectations.
packages/migration/src/types.ts	Updated shebang and import paths/extensions along with type definition.
packages/migration/src/program.ts	Added a shebang directive for immediate execution.
packages/migration/src/migration/index.ts	Standardized import formatting and added a shebang revision.
packages/migration/src/data.ts	Revised import paths to include file extensions.
packages/foundations/assets/fonts/generate-eu-fonts.ts	Replaced legacy path imports with node built-ins and simplified error catch.
.xo-config.cjs	Removed ignored patterns to ensure linting is applied uniformly.

Comments suppressed due to low confidence (1)

packages/migration/test/v0.0.6-v0.0.7/v006_v007.spec.ts:15

• The non-null assertion operator (!) assumes result is always defined, which may mask potential issues. Consider validating result explicitly to ensure stability in unexpected conditions.

expect(result!.filter((res) => res.hasChanged)).toHaveLength(1);

[Copilot]

By omitting the error parameter in the catch block, important error details might be lost during debugging. Consider capturing the error (e.g., 'catch (e)') and logging its message for improved traceability.

Suggested change

	} catch {
	console.warn(
	'You need to install pyftsubset. Check packages/foundations/assets/fonts/README.md for more information.'
	} catch (e) {
	console.warn(
	`You need to install pyftsubset. Check packages/foundations/assets/fonts/README.md for more information. Error: ${e.message}`