Support for rump session & affiliated events

[kaymckelly]

The rump session and affiliated events share some characteristics:

1. The administration is delegated to someone other than general/program chair.
2. They need a web presence that's integrated with the conference.
3. They have a program.
4. They may or may not have reviews.

This is strongly related to the direction IACR takes in future for paper reviews. Historically, the rump session has used websubrev. @cca88 has thought about the paper review problem.

[kmccurley]

It appears whatever they used for eurocrypt 2022 just worked, because they put up the program for the rump session.

[kmccurley]

The hotcrp fork has the ability to create a rump session instance, and that is what recent rump sessions have used (except for small conferences like FSE, where they just do it with email). For the big conferences, they have the ability to generate a program from the program editor and the rumpsession.php page could be modified to show this when it becomes available. The natural way to do this is to include js/program.js and call it to look for json/rump_program.json