Structured data for `attemptType`

[CocoisBuggy]

There has been some confusion about what data exactly to put in this field, and it would benefit us in the long-run to constrain this field for data aggregation purposes.

• [ ] Add an enumeration with reasonable attemptTypes
• [ ] Allow for some array of these attemptTypes to be assigned to a given tick - There is some philosophizing to be done on this point, but realistically you can have some of these types happen in conjunction.
  • [ ] Allow fetching of the enum from the database - This will be a changing set, so we shouldn't hard-code values accross the various services.

[Vichy97]

This should also apply to tick styles. Both should be an enum

[julianlam]

For what it's worth, a tick style doesn't seem to be relevant in a bouldering context. The field should be hidden in front-end, and if not already done so, the backend should allow null as an acceptable value (related; #419)

There are additional restrictions one can add (e.g. does the submitted style and attempt type combination make sense?), so things like Boulder/Pinkpoint are not allowed, but I think that might be overkill.