chore(proofs): anoncreds data integrity namespace change

[rmlearney-digicatapult]

The VC 1.x pathways for anoncreds inside linked-data-proofs currently occupies the data integrity namespace in its file names, symbols and method names

This is a semantic cleanup to prepare for spec-aligned data integrity 1.0 support in credo-ts

• no changes to wire format
• extracted anoncreds VC 1.0 code from linked-data-proofs into anoncreds-w3c-bridge
• ensure hard boundaries inside VC, PEX, DIDComm for special-casing VC 1.0 anoncreds carrying DataIntegrityProof and cryptosuite: anoncreds-2023 to preserve wire formats
• added regression tests to ensure ldp_vc/ldp_vp with dataintegrityproof and anoncreds-2023 cannot enter vc 2.0 data integrity flows
• specific deprecated.ts file containing aliases to ensure minor-version compatibility with 2 getters marked with @deprecated for future removal

[changeset-bot]

🦋 Changeset detected

Latest commit: dd245f3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 18 packages

Name	Type
@credo-ts/core	Patch
@credo-ts/action-menu	Patch
@credo-ts/anoncreds	Patch
@credo-ts/askar-to-drizzle-storage-migration	Patch
@credo-ts/askar	Patch
@credo-ts/cheqd	Patch
@credo-ts/didcomm	Patch
@credo-ts/drizzle-storage	Patch
@credo-ts/drpc	Patch
@credo-ts/hedera	Patch
@credo-ts/indy-vdr	Patch
@credo-ts/node	Patch
@credo-ts/openid4vc	Patch
@credo-ts/question-answer	Patch
@credo-ts/react-native	Patch
@credo-ts/redis-cache	Patch
@credo-ts/tenants	Patch
@credo-ts/webvh	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[rmlearney-digicatapult]

@TimoGlastra as the author of the original code and RFC 0809 I'd really welcome your review on this. I have VC 2.0 with W3C data integrity v1.0 locally implemented and am trying to stage in small reviewable blocks. This namespace change is one important early move to allow for data integrity v1.0