Use consistent Enums between prisma schema and sbem component literal fields

[szvsw]

Mixed feelings on this one; currently, sbem.components is fully independent of prisma, which ideally I would like to keep that way for a variety of reasons.

If we wanted to add enum safety to the database, it would require creating enums in the schema.prisma; these would result in auto-generated types, which could be imported to use in class definitions, but again, I would like to keep sbem.components agnostic as to its database source if possible. If we want to ensure consistency between enums while maintaining independence of components from prisma, we would need to probably have some sort of simple module which imports pairs of relevant types from both sbem.components and prisma and is written to result in a type error if they are not compatible.

This would be less of an issue using SQLModel of course, but that has its own host of issues.