Added a static message to the new registration view notifying new volunteers of the need to be confirmed by an admin.
Updating confirmation notice
Prelim. scale_type model w/ errors
Progress on scales, still error-prone
Migration file addition
Mostly working scale implementation.
Linked schedule parts to scale types.
Work on menu bar
Working scale selection (no conversion)
Fixed a syntax error
Semifinal implementation of selectable scales

This commit contains a functional implementation of regionally-defined scales. This feature allows regional admins to define different scales for their region, which are named and associated with a unit of weight. This commit does not contain a functional unit conversion mechanism - the code is mostly in place, but with the actual conversion dummied out because of some bugs I have yet to tackle.
Completed scale implementation
Final, working scale_types implementation

This is the final implementation of regionally-selectable scales. A new migration file, init_scale_types, will create "Guesstimate scales" for each region, which measure in pounds - this made more sense to me than a separate flippable bit for guesstimates. In order to use actual scales, regional administrators should go to the new Scale Types tab under their menu bar section and create a new scale for the appropriate weight unit. Log_parts are associated with the scale their owner log was measured with, which should make data analysis fairly painless.

Unit conversions are relatively rough, and could definitely be refined - at the moment kg and st are converted to lb with a floating point multiplicative operation and then cast to an int; I don't think this will create a serious amount of error, but I could definitely be wrong there. If it's a problem I'll go in and tinker with them.

The conversions themselves happen at the log-part level; since the values present on the edit-form view for logs are the converted values, the edit action DOES NOT run the conversion. If this becomes an issue I think it would be somewhat easy to check to see if the scale was changed from its original, and run the conversion then, but that seems pretty superfluous now.

If I get the chance, I'd like to add an attribute signifying a given scale's degree of precision - currently, there's no real reason for a region to have multiple (non-guesstimate) scales asside from mixing their weight units.
Misc. fixes after code review.
Merging branch with new changes on main
Misc. fixed (no more weight casts to int)
Merged migration files, indentation fixes
Clipping out redundant scale initialization
Flash notice + relationship fixed pt. 1
indentation fixes, migrate changes