Format Dynamically Generated Labels

[mattwalo32]

Currently much of the frontend (especially on the Profile page), is generated from the backend. This leads to the labeling being a bit weird. For example, some enum options are "SOFTWARE_DEVELOPER" instead of "Software Developer" and labels are of the form "firstName" instead of "First Name".

To fix this, we could either:

1. Make the DB field names/values user friendly
   • This would fix the enum issues, but not the label issue
2. Format fields based on pattern
   • All DB fields are camel case, and enum fields are all capital, so it would be rather easy to derive a readable version of the fields/enums by doing string replacement
   • This would work well provided proper naming convention is always followed when adding enum options/member fields
3. Pass labels to the frontend
   • The backend could instruct the frontend how to display all fields
   • This is the most flexible, but it requires a bit of hardcoding on the backend