refactor: rule optimization

[mfranzke]

Proposed changes

Deactivating a rule in total is quite heavy, we should only take care of specific aspects and probably define things a little bit more granular.

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-rule-optimization

[Copilot]

Pull Request Overview

This PR refactors the rule configuration to optimize how imports are handled, aiming for a more granular approach rather than deactivating rules entirely.

• Updated the configuration for the "import/extensions" rule to enforce specific behavior for TypeScript files.
• Retains the existing configuration for other import-related rules.

Comments suppressed due to low confidence (1)

.xo-config.cjs:35

• Verify that the new configuration for 'import/extensions' does not conflict with 'n/file-extension-in-import'. If both rules are enforcing similar checks, consider consolidating or clarifying their roles to avoid unintended linting errors.

                'import/extensions': [