Feat: Add a `registered_on` column to `user_reg.db`

My understanding is the last_update column could potentially be overwritten by a repeat registration action. That should never happen, but just in case...the registered_on column would contain the date of initial registration for each user.

Having a definitive source of this date is useful for metrics, reporting and facilitation.