fix(AAS List): Handle protected repositories in aas list

[pawel-baran-se]

Description

• fix - Update the AAS List when repository is secured now will ask to login
• fix - Configured and not secured repositories are still available
• refactor - Updated localization for NextJS in affected components
• refactor/fix - Update error notification handling

Fixes # (Issue)

Type of change

Please delete options that are not relevant.

• Minor change (non-breaking change, e.g. documentation adaption)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that causes existing functionality to not work as expected)

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix or my feature works
• New and existing tests pass locally with my changes
• My changes contain no console logs

[GailMelanie]

We agreed some time ago that we want to use camelCase for the localization keys (sorry 😄 )

[pawel-baran-se]

of course no problem :) I was confused because I saw both in the files I gues I had 50 % chance :D

[JonathanXITASO]

Im not a fan of ripping these messages out of the QrScanner group.
For now it is fine, because the QrScanner is not fully translated, but I would highly suggest we move the error messages back, when we actually do the full change.

[pawel-baran-se]

Fine with me I just like to have errors with errors and other stuff with other stuff :) but I will move them back ;) Although I agree maybe having errors group within the QrScanner group would be even more clear. Good point!