resource usage tracker shall keep track of parent project/node IDs

[sanderegg]

### Tasks
- [x] migrate database to get the optional parent project UUID and parent node ID
- [x] upgrade pub/sub call to pass the necessary fields
- [x] return these fields to the frontend

[matusdrobuliak66]

• (Discussed with @odeimaiz ) In the resource usage tracker database table, we will introduce fields like root parent project id and root parent node id (nullable fields).
• When listing usage, if these fields are present, we will substitute project id / project name with the ones from the root, therefore no changes on the frontend are needed.
  • Potentially, we can improve the naming of some nested nodes.
  • Also, consider substitution vs. overwriting directly in the database, as users might search/filter by these fields, and it might be easier for us to avoid introducing additional complexity.

[sanderegg]

all completed