fix(Castor): createPrismDID and resolveDID key id conflicts

[curtis-h]

Description:

Multiple fixes around did resolution:

Bug1: Resolving a PrismDID was overwriting the key ids with our own value fix: src/castor/resolver/LongFormPrismDIDResolver.ts line 124 use the key.id instead of generating our own with getUsageId

Bug2: Creating a PrismDID with multiple issuing keys only encodes one, as the key ids conflict. fix: src/castor/Castor.ts line 146 create the id from both the usage and the index

Bug3: JWT verify required the encoded verification methods to be in order with the signing key first, otherwise would fail fix: attempt verification with all verification methods, as no way of determining which was used

Checklist:

• [ ] My PR follows the contribution guidelines of this project
• [ ] My PR is free of third-party dependencies that don't comply with the Allowlist
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have checked the PR title to follow the conventional commit specification

[github-actions[bot]]

Lines	Statements	Branches	Functions
	75.37% (2788/3699)	65.09% (1356/2083)	80.55% (721/895)

JUnit

Tests	Skipped	Failures	Errors	Time
504	6 :zzz:	0 :x:	0 :fire:	1m 20s :stopwatch: