fix: duplicate offer being created on issuers side while negotiating offer as a holder

[GHkrishna]

What

• Fixes Duplicate credential record as Issuer when OOB offer and negotiateOffer as Holder #2022

How

• Initially during processing proposal in cases where an OOB credential is being offered.
• If holder, accepts OOB invitation and negotiates the offer, the connection details are appended on the holders side.
• But for issuer we are unable to update the credential record with the connection details.
• Hence, the issuer considers this credential proposal as a new flow and creates a new credential record with connection details. This causes the flow to break further in the processing when two records against a single threadId are found

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0a45441

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[TimoGlastra]

Previously we haven't supported proposals for connectionless exchanges. We probably need some additional checks to ensure the exchange can't be hijacked by another connection. You can look at the other methods. And we need to set the connection id after fetching if it's available

[GHkrishna]

@TimoGlastra is this the right approach to associate the connectionId once we get the credentialRecord

[TimoGlastra]

Thank you!