[chore] Reorder columns #2824

[thompson-tomo]

Fixes #2824

Changes

The attribute tables have been re-organised in the following manner:

• Attribute heading added above attribute tables to provide guidance as to what the table is and helps when multiple tables are rendered alongside one another
• Attribute column heading renamed to Key as it relates to the key of the attribute which is a row
• Examples column heading renamed to Example Values as it relates to the value of the attribute rather than an attribute
• Type column heading renamed to Value Type as it relates to the type expected of the value rather than an attribute
• Requirement and stability moved to be after key to give increased focus

The body field tables have been re-organised in the following manner:

• Body Field column heading renamed to Field Name as it relates to the name of the body field which is a row
• Examples column heading renamed to Example Values as it relates to the value of the body field rather than a body field
• Type column heading renamed to Value Type as it relates to the type expected of the value rather than a body field
• Requirement and stability moved to be after key to give increased focus

Note: if the PR is touching an area that is not listed in the existing areas, or the area does not have sufficient domain experts coverage, the PR might be tagged as experts needed and move slowly until experts are identified.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• Links to the prototypes or existing instrumentations (when adding or changing conventions)

[trask]

Examples of new layout, anywhere there's an attribute table.

Stability and Requirement level have been moved closed to the beginning, and a couple of column renames:

[kamphaus]

I think we should have either Summary or Description for both:

[thompson-tomo]

@kamphaus i agree that in the end they should match. I was planning to update the signal property headings/labels is in a follow up pr to not change too much here. That pr would also standardise title casing & : for all labels. I will raise that later this week and link the 2 pr's.

Unless @trask things it would be better to have 1 bigger pr to cover both.

[trask]

I'd suggest leaving it as Description in this PR, and you can follow up later with a PR to propose changing them both at the same time

[thompson-tomo]

FYI @mmanciop this PR implements the reordering of the columns as you suggested.

[thompson-tomo]

@joaopgrassi to avoid the continuous need to resolve conflicts, can you let me know once there is enough approvals and I will do it.

[joaopgrassi]

Let's talk about it on the meeting today and then if no objections we can merge 👍