Removing remaining database triggers

[lampajr]

Fixes Issue

Fixes #2228
Fixes #2231

Changes proposed

Moved the logic to update run_schemas and dataset_schemas into Horreum logic and as a consequence I removed the following entities:

Triggers:

• ds_after_insert
• rs_after_run_untrash
• rs_after_run_update
• before_schema_update

Functions:

• ds_after_dataset_insert_func
• rs_after_run_update
• before_schema_update_func

I kept the procedure update_run_schemas in the db as it is always called by the Horreum directly.

Additionally with commit 714223f I removed the remaining triggers on Run table:

• after_run_update_non_data, moved logic into Horreum
• delete_run_validations, we are not even allowing Runs to be deleted so no need to keep that

With commit d18fcc7 I also removed all triggers associated to the label table:

• lv_before_update
• lv_after_update
• recalc_labels

And related functions. Moreover I also deleted the label_recalc_queue table as no longer used.

Preconditions

• This PR is based on Remove view recalc queue #2203, therefore we have to merge that first and then rebase this one.

Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• My change requires changes to the documentation.
• I have updated the documentation accordingly.
• All new and existing tests passed.

[stalep]

Looks good, the only concern is if we have good enough coverage already in our testsuite with regards to label and label values updates/delete etc. I had a look at the tests and it looks like we are covering quite a bit.
Then if we see any anomalies in testing we are aware of this change and can investigate further.

[lampajr]

Looks good, the only concern is if we have good enough coverage already in our testsuite with regards to label and label values updates/delete etc. I had a look at the tests and it looks like we are covering quite a bit.

That's a reasonable concern!

As part of the latest refactoring I improved the coverage for those logics but for sure it can be improved even further.

Then if we see any anomalies in testing we are aware of this change and can investigate further.

Totally agree on this, I also tried to document as much as I could the methods such that it should (hopefully) be a bit more easier to debug what's going on