Scaffold the Angular library project

[NoNamer777]

Question

Restructure this repo from its current Angular application project into a single Angular library project, scaffolded via `ng generate library` (decided: Angular Library Template).

Concretely:

• Run `ng generate library` to create the library under `projects/` (no separate demo app, library-only, per the map's destination).
• Remove the app-specific bootstrap: `src/main.ts`, `src/index.html`, `src/core/root/` (component, spec, harness), `src/core/config/app.config.ts`, `src/core/config/app.routes.ts`, `src/core/index.ts`, `src/core/test/`.
• Update `angular.json` and the root `tsconfig*.json` files accordingly (drop the `app` project, wire the new library project's build/test/lint targets).
• Give the library's public API (`public-api.ts` or equivalent) one example function and its test, a small, clearly-a-placeholder function that demonstrates the export surface. Exact function content is not a design decision; pick something trivial and self-explanatory.
• Set `package.json`'s `name` to `@dnd-mapp/template-lib-angular` (final naming/publish-metadata details belong to "Rewrite docs and package metadata", but the base name can land here since the library project needs it to build).

No remaining open decisions, this ticket is pure execution of already-settled choices.

[NoNamer777]

Opened #8, which resolves this via ng generate library scaffolding, app-bootstrap removal, and angular.json/tsconfig rewiring as described above. Verified locally: build, test (100% coverage), lint, and tsc -b all pass.

Left open pending review/merge; the PR's "Resolves #2" will close this automatically.

[NoNamer777]

Opened #10, a redo of the earlier #8 (closed unmerged). Same ng-packagr/projects layout as #8, plus the root package.json name and the generated README boilerplate fixed this time. Verified locally: build, test (100% coverage), lint, format, and tsc -b all pass.

Left open pending review/merge; the PR's "Resolves #2" will close it automatically.