make upgrading easier

[BBC-Esq]

The paths to the databases are put into the config.yaml when created. Make it so the paths are relative if possible so that if a user copies and moves the repository folder that it will still work.

Moreover, add a feature to easily upgrade from within the GUI when there's a new release, which will add/remove/update any dependencies, scripts, etc., but keep intact any databases, embedding models downloaded, etc.

[BBC-Esq]

Possible HASH all files within a database after it's created and save. This list of hashes of all files can then be consulted, and if all match, revise the path within the config.yaml file to where the database has been moved, if at all. This can also possibly run on startup to verify a file or nothing has changed with the database files that might cause an error.

Perhaps a "verify_database_integrity" function using the HASH values to both verify the integrity upon startup as well as locate the new path where the database files have been moved to if, for example, a user moves the entire folder. This would necessitate updating all other paths in the config.yaml file as well, however.