Point repository references to eclipse-aascw

[aaronzi]

Problem

The npm publish for the v1.1.0 release (run 38377133716) failed with:

npm error 404 Not Found - PUT https://registry.npmjs.org/aas-package3-typescript - Not found

The repository moved from aas-core-works to eclipse-aascw, but some settings still refer to the old location:

1. npm trusted publisher (not part of this PR, has to be changed on npmjs.com). The trusted publisher is still configured for aas-core-works/aas-package3-typescript, while the OIDC token now identifies eclipse-aascw/aas-package3-typescript. npm answers that mismatch with the 404 above. v1.0.0's provenance confirms it was built in aas-core-works.
2. repository.url in package.json. With --provenance, npm checks that repository.url matches the repository the provenance was built in. Without this change, the next publish would fail at that check.
3. publish.yml. The "Commit synced package files" step only runs when github.repository == 'aas-core-works/aas-package3-typescript', so it has been skipped since the move. That's why package.json on main still says 1.0.0.

Change

• package.json: repository.url now points to eclipse-aascw.
• publish.yml: the repository condition of the sync step now names eclipse-aascw.
• README badges and the link-check ignore pattern updated to the new org. GitHub and Coveralls serve both URLs, so this is cosmetic.

No library code changes. Typecheck, lint and tests pass.

Releasing 1.1.0 after merge

1. Update the trusted publisher on npmjs.com: owner eclipse-aascw, repository aas-package3-typescript, workflow publish.yml.
2. Publish the release from a commit that includes this PR. A re-run of the failed run would build the old tagged commit, which still has the old repository.url.