fix: missing migration script and exports

[genaris]

Unfortunately, migrateDidRecordToV0_3 was not added to updateV0_2ToV0_3 script, meaning that DID records were not upgraded, making DIDs non-resolvable.

This PR fixes that and also exposes a few classes that are mentioned in the documentation but were no exported directly.

[codecov-commenter]

Codecov Report

Merging #1184 (1f0ac8f) into main (e299a03) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1184   +/-   ##
=======================================
  Coverage   88.81%   88.82%           
=======================================
  Files         706      707    +1     
  Lines       16583    16593   +10     
  Branches     2801     2804    +3     
=======================================
+ Hits        14729    14739   +10     
  Misses       1744     1744           
  Partials      110      110           

Impacted Files	Coverage Δ
packages/core/src/index.ts	100.00% <100.00%> (ø)
packages/core/src/storage/migration/index.ts	100.00% <100.00%> (ø)
packages/core/src/storage/migration/updates.ts	100.00% <100.00%> (ø)
...ore/src/storage/migration/updates/0.3-0.3.1/did.ts	100.00% <100.00%> (ø)
...e/src/storage/migration/updates/0.3-0.3.1/index.ts	100.00% <100.00%> (ø)
packages/core/src/utils/version.ts	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[TimoGlastra]

Dangit. We may need to add it as a separate upgrade (like 0.3-patch.1) as agents that have already upgraded won't be able to upgrade again. Thoughts?

[TimoGlastra]

And time to add some tests for this!! Will add soon

[genaris]

Dangit. We may need to add it as a separate upgrade (like 0.3-patch.1) as agents that have already upgraded won't be able to upgrade again. Thoughts?

Well, at the first moment I had the problem that I was on 0.3.0.alpha.xx and when upgrading to 0.3.0 "release" it already thought that I had the last storage version while of course it wasn't.

I think it could be a bit complicated to get version granularity up to alpha level, but maybe it could be possible to do it up to patch version. This way we could add this migrateDidRecordToV0_3 to an updateV0_3ToV0_3_1 that will add an additional step.

[genaris]

And time to add some tests for this!! Will add soon

I've added a test to 0.2 migration considering it will go straight from 0.2.x to 0.3.1, and also a 0.3 migration test that expects to update only DIDs. Working fine also in a 'real-world' 0.3.0 wallet so I hope this will fix the problem as long as most users skip 0.3.0 when upgrading their wallets.

What do you think on supporting patch versions in migrations? Theoretically we'll not need it and we will go now from storage version 0.3.1 to -> 0.4 directly, but if something unfortunate happens (as this issue) we can cover it easily.

[TimoGlastra]

This is great, thanks @genaris. I think patch version migrations should be avoided as it makes updates harder, but yeah totally agree that in such cases it's good to have patch updates