AuthZ (FE) 2: Adding admin components protection.

[KH-Amir-TN]

Description

Adding admin components level protection to handle unauthorized access. TODO: + Check any missed i18n. + Check how to reduce duplication without introducing any complexity. + Check how to make unneeded requests when catching a restricted access. + Add in smart router to detect what default admin page to render when accessing /admin. + Confirm the conformity of the frontend checks to the backend authorizations.

Testing Steps

1. Pull the code.
2. Install the dependencies bundle install && npm|yarn install.
3. Clean the previous assets build by running rm app/assets/builds/* (This won't remove .keep since it's hidden).
4. Clean the database and tmp files for a better isolation by running rails tmp:clear && rails db:schema:cache:clear && rails db:drop && rails db:create && rails db:migrate:with_data
5. Run the linter and specs bundle exec rubocop --parallel && bundle exec rspec && npx eslint app/javascript/* --ext .jsx,.js
6. Run ./bin/dev to run the assets builders processes and the Puma server all at once.

Screenshots (if appropriate):

[KH-Amir-TN]

DEPENDS ON #3984

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication