fix: problem when deleting capture areas

[BeierKevin]

PR description

There was a bug with the capture area array not really updating the rendered list properly because its not reactive etc. The solution may not be really good tho.

Definition Of Done (DoD)

This PR can be squashed / merged if

• a developer is assigned
• the PR is NOT estimated
• the PR is labeled
• the PR is NOT assigned to the current sprint
• a meaningful title has been set according to https://www.conventionalcommits.org/
• the PR is described in detail
• the PR links to an issue
• the PR has been reviewed

Add additional conditions here if necessary for this PR

fix: #186

[roman533]

Simple solution, works

[Claiyc]

This is actually a bigger issue than it seems… We cannot just reassign ca ids, as the VIGAD-API redis db structure relies on them (and therefore potential third party apps as well). A solution may be to have unique ids for capture areas (randomly generated). However for this solution we should provide the ability for a user to manually override the id of a capture area to keep consistency between sessions.

[BeierKevin]

If there should be the option that the user can change the ID of a capture area i need to change a lot ofthings for example should the id then be only a number and what rules should this id follow if any ?

[Claiyc]

If there should be the option that the user can change the ID of a capture area i need to change a lot ofthings for example should the id then be only a number and what rules should this id follow if any ?

I guess it will be easier if it is alphanumeric (so we definitely won't run into issues with collisions). However it needs to be URI conform as well. Other than that, no rules that I can think of. Maybe not too long (idk, 6 characters should be enough?)

[BeierKevin]

If this only alphanumeric isn't it always URI conform ?

[BeierKevin]

This is just a workaround, because i cant fix it really

[Claiyc]

seems to get the job done