Horizon config section for more opinionated best practices

[sreuland]

What problem does your feature solve?

Partner Experience initiative - consolidate horizon config docs section, review and update/refactor the copy to be lighter footprint but with more opinionated direction towards a single group of settings to enable user's to quickly get through it and have a decent running system afterwards, rather than documenting all settings individually and letting the user figure out how to group/associate them:

How much history should they retain?
Should they use in-memory or on-disk mode?
How often should they run state verification? Use the new config params …
What version of postgresql should they run?
How often (hopefully, never) do they need to manually vacuum their db?

What would you like to see?

Updated copy on horizon config in https://developers.stellar.org/docs/run-api-server/configuring

What alternatives are there?