refactor: move DOCUMENT import from @angular/core to @angular/common

[JDavid21051]

What kind of change does this PR introduce? (check one with "x")

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

What is the current behavior? (You can also link to an open issue here)

In an Angular application version 19.

• Swimlane/ngx-datatable version 22.0.0 is installed.
• The NgxDatatableModule is configured.
• The application is served.
• The error is visible.

 X [ERROR] No matching export in "node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@angular/core/fesm2022/core.mjs" for import "DOCUMENT"

node_modules/.pnpm/@swimlane+ngx-datatable@22._0e939b4033fa2a9aedc7471838ba02ad/node_modules/@swimlane/ngx-datatable/fesm2022/swimlane-ngx-datatable.mjs:2:343:
      2 │ ... signal, IterableDiffers, ViewChild, computed, DOCUMENT, ContentChildren, NgZone, input, effect, Ng...

This happens if you use npm or pnpm to install dependencies or serve the application.

#2253

What is the new behavior?

DOCUMENT is now imported from @angular/cli

Does this PR introduce a breaking change? (check one with "x")

• Yes
• No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

Official documentation about DOCUMENT
https://angular.dev/api/common/DOCUMENT