BDMS 389: open and datalogger suitability status implementation for well inventory csv

[jacob-a-brown]

Why

This PR addresses the following problem / context:

• Two fields from the well inventory csv need to be recorded correctly in the status_history table: is_open and datalogger_possible

How

Implementation summary - the following was changed / added / removed:

• If either field is set they get written to the status_history table

Notes

Any special considerations, workarounds, or follow-up work to note?

• The branch well-inventory-csv contains the work done in PR BDMS 389 inspired: status history refactor for wells #299. This was approved to go into staging, but since it modifies the database models it has not yet been merged. Once that is merged into staging the refactoring of putting these fields into the status_history table will be in both staging and well-inventory-csv
• Once this is incorporated into well-inventory-csv all well core and additional information will be accounted for. Next is the water levels

[TylerAdamMartinez]

lgtm

[jacob-a-brown]

@chasetmartin I fixed the merge conflict artifact with erase_data in tests/features/environment.py and pushed it to both well-inventory-csv and this branch. I kept erase_data as False.

[chasetmartin]

Looks good