Shared Filesystems can't be deployed on local-only storage due to "HA" requirement

### problem

The Shared Filesystem appliance requires a "HA enabled" compute offering - and it's not a bad idea, but in cloud with local storage only this becomes a problem as it's pointless to add HA=true to an offering on local storage and could also lead to other possible issues in Cloudstack internally (who knows..).

Is it worth adding a global option, such as "sharedfs.ha.required" and set it to yes/no depending on what storage you are running?

### versions

4.20 KVM

### The steps to reproduce the bug

Deploy Filesystem Share without HA enabled compute offering.

### What to do about it?

Discuss and maybe implement an extra global option to require or not HA in offerings.

Shared Filesystem アプライアンスのデプロイパスと、HA 対応のコンピュートオファリングを必要とするバリデーションから始めます。ローカル専用ストレージと HA なしのオファリングを使ってデプロイを再現し、その後、要件がどのように適用されるかを追跡します。ローカルストレージ向けに動作を設定でき、必要な箇所では現在の HA 要件を維持できれば完了です。

索引モデルが issue の本文から書いたものです。