Update flow of example info

[johnwight]

Taking @gigazelle advice in part on this and changing my mind. The fact that both request and response example appear at same place in layout make the ordering considerations a bit different than I was used to. As a result, I'm putting the both examples first and then adding parameters. I'm also changing the org a bit in other ways as the parameter section is now a sub-unit of each example details section.

Description

Related Issue

Motivation and Context

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:

• I have signed the Adobe Open Source CLA.
• 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.