Case handling, datetime handling and geometry updates

[Milo-Dias]

Problem

• Numeric-looking strings such as "760309" (assetname) and "33,34" (dem_location) were incorrectly interpreted as dates.
• Insert field names became case-sensitive. Issue: Case sensitivity for the insert method #119.
• Geometry updates were sent through the ordinary field-update command and were not saved correctly.

Fix

• dotnet.py: Text values now stay as text unless the destination field is actually a date field.
• queries.py: Insert field names now work regardless of capitalization—for example, both "Description" and "description" are accepted.
• queries.py: Geometries now use the correct MIKE+ geometry update operation.
• queries.py: Apply geometry through UpdateGeomByCommand and raise an explicit error when it does not commit.

[ryan-kipawa]

Great work! I have some feedback that we could iterate on:

1. Add failing tests for all of the fixes. These are new/modified tests that fail on the main branch, but then pass with the fixes of this PR.
2. For case-sensitivity: this may be an issue limited to postgres rather than sqlite. Pinpointing the issue slightly could reveal a solution that's easier to maintain. I partly wonder if this could be handled upstream by MIKE+.
3. The dotnet.py module is intended for code related to Python <--> .NET type conversions. I think the datetime parsing logic should go there - this may require extending it to be aware of the column's data type.

[Milo-Dias]

Great work! I have some feedback that we could iterate on:

1. Add failing tests for all of the fixes. These are new/modified tests that fail on the main branch, but then pass with the fixes of this PR.

2. For case-sensitivity: this may be an issue limited to postgres rather than sqlite. Pinpointing the issue slightly could reveal a solution that's easier to maintain. I partly wonder if this could be handled upstream by MIKE+.

3. The `dotnet.py` module is intended for code related to Python <--> .NET type conversions.  I think the datetime parsing logic should go there - this may require extending it to be aware of the column's data type.

Thank you so much for your feedback Ryan and for your time invested into it, I agree with your three points :)

I will add regression tests covering all that I have touched.

The original case-sensitivity failure was reproduced with an SQLite MIKE+ model, so I will test it out and document it. And investigate whether InsertByCommand should be corrected upstream in MIKE+ or not.

I will also move datetime parsing back into dotnet.py

I will keep you updated,
Thanks :)