chore: get instruction appendix ready for release

[dhower-qc]

This does several things:

• fix(build): make instruction appendix dependent on docs-resources
• fix: remove stray '<' in instruction appendix pages
• refactor: use cfg_arch.possible_instructions to get appendix list
  • Also removes InstructionIndex class (redundant now)
• ci: only generate asciidoc for instruction appendix regress
• ci: add instruction appendix to deployment

I'll also add a regression to check a "golden" output.

[AFOliveira]

LGTM so far. Will you also add the assembly field to the erb template or do you prefer me to do so in a separate PR?

[AFOliveira]

@dhower-qc is it fine with you if I add a commit with a Assembly field being reliant on an environment variable?

[dhower-qc]

@dhower-qc is it fine with you if I add a commit with a Assembly field being reliant on an environment variable?

What would that look like?

[AFOliveira]

My idea was to add a couple lines to the erb template that prints the Assembly field if "ASSEMBLY=1".

[dhower-qc]

ahhh, I see. I thought you meant a variable that changes the string.

I have no problem with ASSEMBLY=1