Bugfix/fix sqlite holidays and excess data

[Chris-May]

Sqlite

This fixes the issue where the sqlite database was not getting populated by anything other than the base_price table.

In sqlite, an INSERT statement implicitly opens a transaction, which needs to be committed before changes are saved in the database.

I added the commit command to do so and updated the documentation.

Duplicating data on each sqlite connection

Every time the code connects to a sqlite database, it adds the same data to the database.

This is one way to fix that by trying to query the last piece of data expected in the database. If it's there, it returns early. Otherwise it'll run the code to add all the data.

Fix: holidays throw "string has no attribute year"

When a request is for a day pass and has a date, the logic it tries to compare the request's date to the date that comes from the database.

However, when sqlite pulls data out of the database, it's a string. It needs to be converted to a datetime object.

This is one way to fix this issue. I'm very open to other suggestions.

[codecop]

Thank you.
We also need these changes on with_tests please.
Could you see if you can add to the Github build action and also run tests for Python using SQLLite, so both DB connecivities are tested?