Description

Configuring the code to optionally load in initial algorithms after the tables have been initialized. Doing so, removes our needs now for having to use a database migration tool for the near future.

Related Issues

closes #57

Additional Notes

• This is contentious, but have removed alembic. Using alembic has required a lot of manual effort to get migrations correct, with little benefit this early in a project. Our schema hasn't stabilized yet, and we don't have any systems running the code in production, so it's of little value. Over time, we may need to bring this back to safely adjust production schemas, but now is not the time.
• Created assets/initial_algorithms.json with the two existing DIBBs algorithms. We can use this for our test cases, and also initializing a new database with the data, if the INITIAL_ALGORITHMS env variable is set. This also gives customers another option for managing their algorithms, in they can write their own and set the INITIAL_ALGORITHMS env variable to load that json file.
• Capitalized schemas.pii.Features. The blocking keys were capitalized, so making them both capitalized will hopefully reduce errors in writing the algorithm specs.
• Consolidated some of the assets and testing assets, as there were duplicates and there was some testing files in the top level one.

<--------------------- REMOVE THE LINES BELOW BEFORE MERGING --------------------->

Checklist

Please review and complete the following checklist before submitting your pull request:

• I have ensured that the pull request is of a manageable size, allowing it to be reviewed within a single session.
• I have reviewed my changes to ensure they are clear, concise, and well-documented.
• I have updated the documentation, if applicable.
• I have added or updated test cases to cover my changes, if applicable.
• I have minimized the number of reviewers to include only those essential for the review.

Checklist for Reviewers

Please review and complete the following checklist during the review process:

• The code follows best practices and conventions.
• The changes implement the desired functionality or fix the reported issue.
• The tests cover the new changes and pass successfully.
• Any potential edge cases or error scenarios have been considered.