refactor: make use of the new cc-notice in place of cc-error

[Galimede]

Context

With the addition of the new cc-notice component there are places where we could use it instead of our actual cc-error component.

Components concerned

• [ ] cc-addon-admin (handled by #777)
• [x] cc-addon-backups
• [x] cc-addon-credentials
• [x] cc-addon-elasticsearch-options
• [x] cc-addon-encryption-at-rest-option
• [x] cc-addon-linked-apps
• [x] cc-addon-features
• [x] cc-addon-jenkins-options
• [x] cc-addon-mongodb-options
• [x] cc-addon-mysql-options
• [x] cc-addon-postgresql-options
• [x] cc-addon-redis-options
• [x] cc-addon-option-form (in story, slotted)
• [x] cc-addon-option (in story, slotted)
• [x] cc-article-list
• [x] cc-block (in story, slotted)
• [x] cc-doc-list
• [x] cc-elastic-search-info
• [x] cc-jenkins-info
• [x] cc-email-list
• [x] cc-env-var-create
• [x] cc-env-var-editor-expert
• [x] cc-env-var-editor-json
• [x] cc-env-var-linked-services
• [x] cc-env-var-form
• [x] cc-grafana-info
• [x] cc-header-addon
• [x] cc-header-app
• [x] cc-header-orga
• [x] cc-heptapod-info
• [x] cc-matomo-info
• [x] cc-pricing-estimation
• [x] cc-pricing-product
• [x] cc-pricing-product-consumption
• [x] cc-map
• [x] cc-tcp-redirection-form
• [x] cc-tile-consumption
• [x] cc-tile-deployments
• [x] cc-tile-instances
• [x] cc-tile-requests
• [x] cc-tile-status-codes
• [x] cc-invoice-list
• [x] cc-zone-input

Problem

A few tests has already been made on some components and already some problems were found:

• components like cc-header-* are weird looking with the whole notice in the "box" on error
• it also seems to not be a valid option on components that have the cc-error on the front with the background of the component blurred on error

[Galimede]

Update (2023-04-07)

As of today, every components have been switched from cc-error to cc-notice with some exceptions. Indeed these components have not been changed for various reasons:

• cc-addon-admin => there's a cc-error on top of the addon-admin block. Putting a cc-notice with blur in the background shouldn't be the way to go.
• cc-addon-*-options => I've tried to change it from cc-error to cc-notice. But I wonder if the notice is too much visible.

before:

after:

• cc-tile-* => While I kept the change, I feel like cc-notice is too small on the tile components.
• cc-map => there's a cc-error on top of the blurry map. Putting a cc-notice with blur in the background shouldn't be the way to go.
• cc-env-var-* => I feel like it's good but maybe a bit too big :thinking:
• the pricing components have not been handled as it will be done from the current pricing PR.

Feel free to give feedbacks on the screens (changes from the screens are not made in the code yet) and the information above.