Dynamic Ticket Types to Replace Hardcoded Values

[nolotz]

Currently, the ticket types are hardcoded within Ticket::TYPES. This approach, while straightforward, limits the system's flexibility and adaptability. In scenarios where different or additional ticket types are needed, the hardcoded list becomes a constraint.

I propose implementing a more dynamic system for managing ticket types. This could involve allowing ticket types to be defined and managed through the settings panel.

I would love to hear your thoughts on this proposal. Does this idea align with your vision for Bileto? Are there any specific considerations to keep in mind for implementing such a feature?