Configurable reservation view

[esune]

Acceptance Criteria:

• The form in the reservations view is configurable: the required fields can be configured for each instance
• The required fields (email, tenant name) are always required
• Data structure in backend is JSON blob, not individual columns
• Innkeeper view should account for unpredictable length in data when displaying it
• Keep it as simple and light as possible, no unnecessary dependencies or additional services

[loneil]

Will need to consider where the "form schema" (IE the customization of what the reservation form should be) is kept.
Easiest is probably just Tenant UI configuration (with the other env vars). Alternatively could be in the persistence layer of the Innkeeper plugin with an endpoint to get/update it, etc.

So not add any database to the Tenant UI itself as part of this ticket or anything.

[esune]

@loneil agreed.

In the past I used Angular Formly which allows for a JSON template to be specified and loaded at runtime. Similarly, SurveyJS was used in issuer-kit to allow forms to be dynamically rendered at runtime.

Somrthing similar to this would probably be ideal, as it allows for a template to be defined and injected in the Tenant UI and the data to be stored as a JSON blob in the current database (that will likely require some "massaging").

[hiteshgh]

Assigned @popkinj

[loneil]

Added block on this ticket for #773

cc @popkinj @esune @hiteshgh

Not sure if 'block' is appropriate, but noting this can't really merge in without accounting for backend (and merging in is probably Definition of Done for tickets)

[hiteshgh]

unblocked

[esune]

Resolved by #645