refactor(services): ent-4669 move config to serviceConfig

[cdcabrera]

What's included

• refactor(services): move config to serviceConfig
  • authentication, flip to platform redux action
  • platform, userActions, move authorizeUser
  • platform, userTypes, move authorize user type
  • userReducer, flip to platform redux types
  • userSelectors, passthrough for transformed responses
  • services, move config to serviceConfig
  • serviceConfig, expand cancel ability to url funcs
  • platformServices, schemas, transformers, mock calls
  • rhsmServices, testing naming for consistency
  • userServices, remove deprecated authorizeUser func

Notes

• This PR is an interim step intended to get the service layer in a position to
  • treat both API and global methods as service calls which allow us to programmatically maintain/generate parts of our state layer (Redux) because everything generates a similar response
  • apply transforms and schema checks to global platform methods
  • allow removing the userSelector, where we currently perform transforms for our "session" state, and move towards authentication context and a session hook
• The primary testing concerns with this PR are
  • we moved the transformations from "userSelector" into a "platformTransformer" ... if the GUI renders correctly is the basic platform check... if we messed up none of it would show up, it's pretty sensitive
  • we moved the function that performs the primary Axios service configuration... checking to make sure all service calls come through, and that if a service call is hit multiple times a "cancel" and "cache" are returned (the check is to make sure only one network call is being performed with the 10 second extended caching setting)

How to test

Coverage and basic unit test check

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

Local run check

1. update the NPM packages with $ yarn
2. $ yarn start
3. confirm product views render as normal

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. confirm product views render as normal

Example

...

Updates issue/story

ent-4669