Move more useful information higher on instruction display page

[ThinkOpenly]

Is your feature request related to a problem? Please describe.
If the primary audience for the RISC-V ISA Manual instruction pages is programmers/engineers, then the order of the information displayed could be better. Currently, the information is displayed in this order:

• name
• long name
• defining extension/version
• containing profiles
• encoding
• assembly syntax
• synopsis
• valid access modes
• decode variables (how to extract fields from the opcode)
• implementation (IDL/Sail code)
• exceptions

Describe the solution you'd like

• name
• long name
• assembly syntax
• synopsis
• execution
• exceptions
• encoding
• decode variables
• defining extension (although a better use of space would be to the right of the name)
• valid access modes
• containing profiles

Additional context

[kbroch-rivosinc]

Here's a table to help visualize this change:

Before	After
1-name	1-name
2-long name	2-long name
3-defining ext/ver	6-assembly syntax
4-containing profiles	7-synopsis
5-encoding	10-implementation (IDL/Sail)
6-assembly syntax	11-exceptions
7-synopsis	5-encoding
8-valid access modes	9-decode variables
9-decode variables	3-defining ext/ver
10-implementation (IDL/Sail)	8-valid access modes
11-exceptions	4-containing profiles

I don't have a strong opinion on the ordering but more that we should condense some of the output to make all of it close to fitting on a single page. Right now as you have shown https://riscv-software-src.github.io/riscv-unified-db/manual/html/isa/isa_20240411/insts/bge the worst is "containing profiles" which can be upwards of 15 LOC which takes up 1/2 page.

Rather then listing one profile per line, I would just have a single line of comma separate profiles and an abbreviation for "Mandatory"

ex: "in profiles: RVA20S64 (M), RVA20U64 (M), RVA22S64 (M) (M = Mandatory)"

[dhower-qc]

1. I suggest we keep implementation (IDL/Sail) after encoding/decode variables since the implementation is going to reference those fields.
2. For the profiles, we could also display it in a table format (with the profile names rotated so they are vertical)

RVA20S64	RVA20U64	RVA22S64	...
M	M	M	...

[ThinkOpenly]

1. I suggest we keep implementation (IDL/Sail) after encoding/decode variables since the implementation is going to reference those fields.

Moving "decode variables" up above "execution":

1. name
2. long name
3. assembly syntax
4. synopsis
5. decode variables
6. execution
7. exceptions
8. encoding
9. defining extension (although a better use of space would be to the right of the name)
10. valid access modes
11. containing profiles

3. For the profiles, we could also display it in a table format (with the profile names rotated so they are vertical)>
   RVA20S64 RVA20U64 RVA22S64 ...
   M M M ...

I thought about suggesting a table, but was worried its width would be unbounded over time.

I'm OK with a list, or lists:

Optional: RVA20S64, RVA20U64
Mandatory: RVA22S64, ...

Lists will wrap as needed to fit the display.