Minor reorganization and cleanup of config

[cdibella]

--- Provide a general summary of your changes in the Title above -->

Description

I added a few more section headers and moved/grouped some of the like things together. I didn't touch most of what was in the first "most frequently changed" section, except for an occasional typo or clarity cleanup.

When additional configuration options are added, they should be added to the appropriate section or have a new section heading if they're not part of an existing topical area. As much as possible, each option in the config file should have an explanatory comment or example.

Related JIRA Ticket or GitHub Issue

Motivation and Context

Many options for the application and its administration can be controlled through the config file, but the file itself is somewhat confusing to navigate. This is a first step toward cleaning it up a bit.

Further work, including breaking this long file up into multiple files or enabling more to be changed via the frontend interface, may be warranted, but for now I was just aiming to make it a little easier for a user to work through the config file its current format.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[gwiedeman]

@lmcglohon I'm not sure why tests failed with "Artifacts support disabled for pull requests." It failed for me locally as well, but I don't really know why. It runs fine for me and all the changes in the config file appear to be superficial. Is there a reason not to merge this?

[lmcglohon]

@gwiedeman There should be no reason not to merge this. I am currently working on other test failures, so feel free to merge this if you think it is good to go.