docs: describe some troubleshooting steps for dependency issues

[mirceanis]

Add a troubleshooting guide and link to it from different tutorials.

Kudos to @theblockstalk for surfacing these issues and their fixes.

[theblockstalk]

for yarn berry (v2+) this solution is needed:
digitalcredentials/jsonld-signatures#8

"resolutions": {
    "jsonld": "npm:@digitalcredentials/jsonld@^6.0.0"
  },

for all versions of yarn, if you want it to bundle and compile in expo (React Native) then this is needed in package.json
digitalcredentials/jsonld-signatures#9

"resolutions": {
        "isomorphic-webcrypto": "link:./node_modules/@sphereon/isomorphic-webcrypto"
    },

lastly, not sure if such changes are also needed when using npm. I would assume they cant hurn. This uses the "overrides" field in package.json
https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides

[nklomp]

Yeah it is a pretty bad situation for RN. The real culprit is in the bad crypto support in RN. We are these days moving to hardware supported crypto only with a new Veramo compatible KMS that can do yubikeys, secure elements, remote HSM, eSIMs etc, so all we need is a RNG / hash functionality. So we have moved to react-native-quick-crypto. That one is nice anyway also for other crypto functions.

The issue is that some of the digital credentials lib require isomorphic-webcrypto, which IMO is a terrable lib and heavily outdated. We only forked it to get it a bit up to date. IMO they should not be using the lib to set the crypto global. Or at least they should check whether it is not already present, and only then set it.