Add tags to Resource Tracker (Reporting)

[mguidon]

Add the possibility to use tags to help with reporting of project costs. (req. by Jacqueline)

### Event Horizon

### Tasks
- [ ] https://github.com/ITISFoundation/osparc-simcore/pull/6722
- [ ] Create needed tags with Nik and Jacqueline

[odeimaiz]

What happens if later the Project gets untagged? Or tags change?

[matusdrobuliak66]

What happens if later the Project gets untagged? Or tags change?

I will enhance the resource tracker so that for specific fields (starting with tags, but potentially adding project names, ..), it will always display the latest up-to-date value or the last up-to-date before it was deleted.

[matusdrobuliak66]

• Goal/Current Use Case:

  • The financial department wants to create tags corresponding to billed projects. Users will then add these tags to the studies they are working on. (This should also be possible retrospectively.)
  • When a CSV file with resource usage is exported, it should include the project tags.

• Current Challenges:

  • Currently, the resource tracker stores all information only at the start of the service run. This approach is insufficient because tags need to be added retrospectively.
  • Simply joining the current project_tags table poses an issue: if a project is deleted, its information would be lost and would no longer be listed. (Currently, the RUT maintains the complete history of runs, so it needs access to the project tags even after the project are deleted.)

• Proposed Solutions:

  1. Primary Solution:
     Use the project_tags table, but instead of deleting rows when a project is deleted, mark them as deleted. This ensures they are not listed anymore but remain accessible for historical purposes.

  2. Alternative Solution:
     Keep a second copy of the project_tags table in the RUT. However, this introduces challenges in maintaining synchronization—not only when a tag is added or removed from a project, but also when the tag resource itself is deleted or updated. (started to implement but I do not think it is a good way to go: https://github.com/ITISFoundation/osparc-simcore/pull/6708)

I found solution 1. more reasonable to implement.

• Implemented behavior:

  • Always display the latest project tags in the listing of service runs.
  • If a project is deleted, retain and display the previously associated tags in the listing.
  • If a tag resource is deleted, the tag will also be removed from all previous service runs.
  • If a tag resource is renamed, it will be updated across all previous service runs.

[matusdrobuliak66]

TODO: create needed tags with Nik and Jacqueline