Support multi-scope configuration settings

[abh1sar]

Doc PR for apache/cloudstack#10300

---

📚 Documentation preview 📚: https://cloudstack-documentation--476.org.readthedocs.build/en/476/

[abh1sar]

@blueorangutan docbuild

[DaanHoogland]

@blueorangutan docbuild

not sure if the ape accepts corrections ;)
@blueorangutan docbuild

[blueorangutan]

@DaanHoogland a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress.

[blueorangutan]

QA-Doc build preview: https://qa.cloudstack.cloud/builds/docs-build/pr/476. (QA-JID 306)

[shwstppr]

@abh1sar can you please add a diagram depicting hierarchy for different scopes?

[abh1sar]

@abh1sar can you please add a diagram depicting hierarchy for different scopes?

@shwstppr although we have defined a hierarchy for each scope in the code, this general information is not useful for the admin, unless we are talking about specific settings and their scopes.
I mean to say no setting currently is configurable at both cluster and zone levels. So even if we mention that zone is the parent of cluster scope, it is not usable by the admin.
Information on hierarchy is more useful for developer who are changing the scope of a configuration.
So I didn't put it in the installguide/configurations sections. Should we put that info someplace else?

[shwstppr]

@abh1sar can you please add a diagram depicting hierarchy for different scopes?

@shwstppr although we have defined a hierarchy for each scope in the code, this general information is not useful for the admin, unless we are talking about specific settings and their scopes. I mean to say no setting currently is configurable at both cluster and zone levels. So even if we mention that zone is the parent of cluster scope, it is not usable by the admin. Information on hierarchy is more useful for developer who are changing the scope of a configuration. So I didn't put it in the installguide/configurations sections. Should we put that info someplace else?

I see it has been added to code PR description which should be enough for now.

[shwstppr]

Minor comment otherwise lgtm

[shwstppr]

should we emphasize somewhere level = scope?

[harikrishna-patnala]

LGTM