refactor(config): sw-722 activate rhel archs filter

[cdcabrera]

What's included

• refactor(config): sw-722 activate rhel archs filter

Notes

• Activates RHEL architectures as a filter
• This update should be coordinated with removal of the left navigation

How to test

Coverage and basic unit test check

1. update the NPM packages with $ yarn
2. $ yarn test
3. confirm tests come back clean

Proxy run check

1. update the NPM packages with $ yarn
2. make sure Docker is running, plus on network, then
3. $ yarn start:proxy
4. navigate to RHEL all
5. confirm the architectures toolbar filter exists and that it can be used to filter for RHEL architectures
   • if the left navigation exists it may have an odd behavior, throw errors, or simply not work... this is expected

Check the build

1. update the NPM packages with $ yarn
2. $ yarn build
3. confirm tests come back clean

Example

Expected navigation using current structure
** surrounding links should be expected to alter between environments. the only links we directly control are underneath the Subscriptions section**

Updates issue/story

sw-722
relates #1006 sw-630

[codecov-commenter]

Codecov Report

Merging #1014 (958fabe) into dev (2891b10) will decrease coverage by 0.10%.
The diff coverage is 91.54%.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1014      +/-   ##
==========================================
- Coverage   93.19%   93.09%   -0.11%     
==========================================
  Files         118      121       +3     
  Lines        3851     3966     +115     
  Branches     1547     1597      +50     
==========================================
+ Hits         3589     3692     +103     
- Misses        244      256      +12     
  Partials       18       18              

Impacted Files	Coverage Δ
src/components/toolbar/toolbarFieldGranularity.js	100.00% <ø> (ø)
...c/components/toolbar/toolbarFieldSelectCategory.js	67.30% <0.00%> (-5.61%)	⬇️
src/components/toolbar/toolbarFieldUom.js	100.00% <ø> (ø)
src/config/product.rhel.js	72.34% <ø> (ø)
src/config/product.satellite.js	75.67% <ø> (ø)
src/config/routes.js	100.00% <ø> (ø)
src/components/toolbar/toolbarContext.js	86.48% <60.00%> (-10.34%)	⬇️
src/components/productView/productViewContext.js	97.87% <100.00%> (+0.57%)	⬆️
src/components/toolbar/toolbar.js	100.00% <100.00%> (ø)
src/components/toolbar/toolbarFieldArchitecture.js	100.00% <100.00%> (ø)
... and 11 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2891b10...958fabe. Read the comment docs.

[cdcabrera]

related menu deactivation in stage-beta, RedHatInsights/cloud-services-config#1363

[mirekdlugosz]

When changing left nav, we should introduce analogous changes in deploy/frontend.yaml.

This file will be used to create menu in ephemeral environment, used as part of PR check. So the correct order of merges would be:

• cloud-services-config is merged and deployed to stage-beta
• iqe-curiosity-plugin PR is merged and tagged, so container is built
• curiosity-frontend deploy/frontend.yaml changes are merged / sent as PR - PR check will use iqe-curisioty-plugin container image, which will now expect changed menu structure

But all three should happen close to each other. Otherwise, we risk spurious tests failures in Jenkins or PR check.

Since #1008 is not merged, we can introduce changes to deploy/frontend.yaml later.

[cdcabrera]

we like the idea of just updating deploy/frontend.yaml as a separate commit with this PR... we'll go ahead and do it... and then activate the PR 1363 on the config side