Change procedure to include Consumers

[egekorkan]

As asked in the testing call, here is a PR that includes putting Consumer implementation information

[mmccool]

so we really should have a consumer.csv and producer.csv if we want to split up assertions

[mmccool]

Discussion (Testfest mtg 2022.10.05):

• Do need to have more discussion on how to test profiles; they make more mandatory constraints on consumers than TDs
• Capture information about which assertions apply to producers, consumers, or both (e.g. an extra column in the manual.csv table)
• Capture information about whether a given implementation is a producer or a consumer - can be in Implementation Description (needs cleanup, discussion of categories)
• Generate report showing coverage of pairwise interaction, i.e. interop matrix - many need one matrix for each profile (or allowed combinations of profiles, eg. baseline + SSE)
• Require two implementations of producers and two of consumers that can interoperate

[mmccool]

Useful to do, and current procedures are working towards this, but I'd rather not change instructions for past events, so closing without merging. Please resubmit if you want to the current event.