[DPE-4759] Bump version

[marceloneppel]

Issue

_on_upgrade_charm_check_legacy() logic is leading to a slow bootstrap of replicas.

This method is not needed anymore (only when upgrading from revision 288).

Solution

Bump the version in src/dependency.json so that after the next stable, we can bump the restrictions (upgrade_supported field) to allow the upgrade only from the latest stable (which will allow us to remove _on_upgrade_charm_check_legacy()).

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.72%. Comparing base (885ab0c) to head (59a5d94).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #510   +/-   ##
=======================================
  Coverage   69.72%   69.72%           
=======================================
  Files          11       11           
  Lines        2870     2870           
  Branches      508      508           
=======================================
  Hits         2001     2001           
  Misses        763      763           
  Partials      106      106           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[taurus-forever]

2 @carlcsaposs-canonical should we use charm version 2 here or better 1.0.1 or alike , re: versioning on upgrade.

[carlcsaposs-canonical]

2 @carlcsaposs-canonical should we use charm version 2 here or better 1.0.1 or alike , re: versioning on upgrade.

this uses the upgrade lib, not router/opensearch/mongodb shared code, so no clue

router/opensearch/mongodb default behavior is to mark major version changes as incompatible

I think the lib uses "upgrade_supported", but believe you have to predict the future there (i.e. it checks the value in the old charm) IIRC, but not sure if that's changed