Update section "Interop Testing"

[nissimsan]

https://w3c-ccg.github.io/traceability-interop/draft/#interoperability-testing

To be updated with the actual approach to interop testing:

• Discovery through did:web
• Pre-issued JWT (to avoid having to call /issue)
• OAuth Client Credentials authentication
• Successful call to /presentations

[TallTed]

Section numbers change. Please always reference them by title, which may include, but should not be reduced to, the number.

[nissimsan]

With #660 we can drop the first bullet point

[PatStLouis]

There is still a concern for me that we need an endpoint available to test an implementation's comprehension of another implementation's issued VC. This would ensure that the libraries used by implementation X can understand the output of libraries used by implementation Y when it comes to verifying proofs, revocation status, verificationMethods representation etc...

[mkhraisha]

There is a proposal here: #659 (comment)

If we agree on that we can go ahead and udpate the spec language on how to do interop tests to reflect our new thinking

[brentzundel]

assign me