[FEATURE] v2 volume supports auto salvage

[derekbit]

Is your feature request related to a problem? Please describe (👍 if you like this request)

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Some discussions
https://suse.slack.com/archives/C02DR3N5T24/p1713926457976349

[DamiaSan]

See data consistency in #7031

[longhorn-io-github-bot]

Pre Ready-For-Testing Checklist

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:

• Does the PR include the explanation for the fix or the feature?

• Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
  The PR for the YAML change is at:
  The PR for the chart change is at:

• Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)?
  The PR is at:

  • feat(auto-salvage): v2 support go-common-libs#70
  • feat(auto-salvage): v2 support types#28
  • feat(auto-salvage): v2 support longhorn-spdk-engine#222
  • feat(auto-salvage): v2 support longhorn-instance-manager#675
  • feat(auto-salvage): v2 support longhorn-manager#3170

• Which areas/issues this PR might have potential impacts on?
  Area v2-volume, auto-salvage
  Issues

• If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted?
  The LEP PR is at feat(lep): auto-salvage support for v2 volumes #9486

• If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)?
  The UI issue/PR is at

• If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)?
  The documentation issue/PR is at doc(1.8.0): auto-salvage support for v2 volumes website#994

• If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*)
  The automation skeleton PR is at
  The automation test case PR is at test(robot): v2 volume should block trim when volume is degraded longhorn-tests#2114
  The issue of automation test case implementation is at (please create by the template)

• If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)?
  The engine automation PR is at

• If labeled: require/manual-test-plan Has the manual test plan been documented?
  The updated manual test plan is at

• If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
  The compatibility issue is filed at

[chriscchien]

Verified pass on longhorn v1.8.0-dev(longhorn/longhorn-manager@a503949)

Test steps:

1. Dynamic provision a v2 volume, having data in the mount point.
2. Set auto-salvage to false
3. Force delete all v2 volume instance-manager pod.
4. V2 volume become faulted and remains in that state.
5. Set auto-salvage to true
6. The faulted v2 volume become healthy and data in the workload is correct.
7. Force delete all v2 volume instance-manager pod again.
8. V2 olume become faulted then healthy again.
9. After volume healthy, data in workload correct.

In v1.7.2, set auto-salvage to true and force delete all v2 volume instance-manager pod, the v2 volume will loop from faulted -> attaching -> faulted.