common_migrations: add new migrations to handle settings-generator as…

… struct

- RemoveWeakSettingsMigration: When we downgrade multiple version to a
  version where migrator is not aware of deleting the setting-generator
 as struct or the strength file. This migration will help us to delete
the strength and setting generator metadata.

- RemoveSchnauzerMigration: This will remove metadata(always) and data
  if the value matches with the value in existing datastore.

- RemoveDataMigration: This will remove the data when value matches with
  existing data.

- ResetMetadataMigration: Migration to remove all metadata on upgrade
  and downgrade. This metadata will be rewritten by storewolf.

This migration will be used to convert a strong setting to a weak
setting.

Also deleted the test test_replaces_nothing for
ReplaceSchnauzerMigration because we are deleting all the metadata as
first step of the migrator, hence we will not have any metadata
available in existing datastore to compare. We will assume that the
settings generator in input metadata is same as Old schanuzer string and
will always replace that with incoming setting generator string.

sources/api/migration/migration-helpers/Cargo.toml

@@ -12,6 +12,7 @@ exclude = ["README.md"]
 bottlerocket-release.workspace = true
 datastore.workspace = true
 handlebars.workspace = true
+models.workspace = true
 schnauzer.workspace = true
 serde.workspace = true
 serde_json.workspace = true