Automatically refresh ACL information in sharing db

[sampsapenna]

Description

Add automatic synchronization for ACL information in sharing database. I.e. current container access additions, removals, edits and container removals.

Previously the sharing information had a tendency towards containing stale data, since people would also access the sharing information in the CLI, remove containers, etc. leading to ACLs changing without updates.

Related issues

• Fixes Better ACL information synchronization #305

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update (this needs a follow up PR)

Changes Made

• Make ACL synchronization run automatically upon login (scheduled on main App creation event)
• Make ACL synchronization a proper background operation to prevent unresponsive UI during sync (force yielding execution in container ACL metadata fetch loop)

Testing

• Unit Tests
• Integration Tests
• Tests do not apply
• Needs testing (start an issue or do a follow up PR about it) UI integration tests for ACL information synchronization #424

Mentions

[csc-felipe]

I'm not familiar with the ACLs yet, and I did not run it, as I haven't been running the whole environment yet. Thus, only looked at the code and made the review as a comment.

I would have preferred if the formatting had been a separate PR, as there's a lot of it.

[blankdots]

if my understanding is correct this #69 is not required any more.

We need to add a follow-up issue to add some integration (or cypress) tests for this. A test could look like:

1. we log in we see some shared containers
2. we update the db in the background
3. we re-login the users we see the updated shared containers

I have not tested, however the code looks good and if we spot any issues I assume we will see them in practice.

also this needs a rebase

[sampsapenna]

if my understanding is correct this #69 is not required any more.

We need to add a follow-up issue to add some integration (or cypress) tests for this. A test could look like:

1. we log in we see some shared containers
2. we update the db in the background
3. we re-login the users we see the updated shared containers

I have not tested, however the code looks good and if we spot any issues I assume we will see them in practice.

also this needs a rebase

Opened an issue for the integration tests in #424

#69 is not relevant to this PR, but it would go nicely together with this change. This PR was about keeping the database information as current as possible. I'd like to keep it open still.

Rebase will happen shortly 👍🏼

[sampsapenna]

I'm not familiar with the ACLs yet, and I did not run it, as I haven't been running the whole environment yet. Thus, only looked at the code and made the review as a comment.

I would have preferred if the formatting had been a separate PR, as there's a lot of it.

Yup, the formatting was an unfortunate mishap with vscode auto-formatting that I noticed too late, thus it made its way in