fix: lock geolocation in forms

[ChasNelson1990]

Description

This PR (and one in bahis-serve) are an attempt to solve the geolocation problem described in #60 and elsewhere.

Essentially, there are two fairly big changes:

1. We store the user's upazila ID in the local DB an use this as "truth" for the user's geolocation
2. Whenever a form is loaded we hide the geolocation fields from the user; we then fill this fields based on the user's upazila in the local DB

TODO / questions

• [x] we have changed how a db is prepared - how will this impact existing users with existing dbs? We don't want users to have to delete their local db so we should catch this - maybe on sync? Or can we do it as part of the update?
• [ ] the bahis-serve change related to this is going to lock users like rupsa out of their accounts - because their account is a district account and not an upazila account. How shall we handle this?
• [x] are existing bahis-desk versions compatible with the bahis-serve changes? if not we can use the version parameter catch

closes #60 requires road86/bahis-serve#14

Database Changes (delete if not applicable)

Yes, when a new DB is 'prepared' it will now force upazila to be an integer and not text.

Checklist

• [x] I have read the road86 Contribution Guide.
• [x] I have checked all commit message styles match the requested structure.
• [x] My code follows the style guidelines of this project.
• [x] I have performed a self-review of my own code.
• [x] I have assigned at least one reviewer.
• [x] New and existing unit tests pass locally with my changes.
• [ ] I have added tests that prove my fix is effective or that my feature works.
• [x] My changes generate no new warnings.
• [ ] I have made corresponding changes to the documentation.
• [x] New database changes have been committed.

[ChasNelson1990]

My latest commit now catches users logging in with an existing local users table. If there is no upazila in it, it drops that table, creates a new one and then logs in as if it was the first time - other existing tables shouldn't be modified by this and so users shouldn't need to run a sync like a real first-time user would.

I have tested this using latest commit bahis-desk with dev-server bahis-serve; it's fine as the old bahis-serve doesn't return an upazila this catch is caught on every log in. This scenario shouldn't happen as we roll out bahis-serve changes before bahis-desk.

I have tested this using latest commit bahis-desk with latest commit bahis-serve; it's fine as this is exactly what the catch is written for.

I have tested this using previous release bahis-desk with latest commit bahis-serve; it's fine as the old bahis-desk just ignores the spare upazila field returned by new bahis-serve.

[mixmixmix]

Whenever a form is loaded we hide the geolocation fields from the user; we then fill this fields based on the user's upazila in the local DB

So we are "hard coding" the upazlia location for all forms? Seem like a good enough hack.

[ChasNelson1990]

So we are "hard coding" the upazlia location for all forms? Seem like a good enough hack.

Aye.