Use webpack alias

[thekp]

Resolves #2567

Overall change:
This continues the work from this PR: #3542
Uses webpack directory aliasing previously set up in #3318
Cypress is not using the Aliases because it can not properly compile the aliases without webpack config

Code changes:

• create a file that contains all the alias and it's formatting in an object to be imported in various places (webpack config, eslint config and jest config)
• updated files that can use the alias

---

• I have assigned myself to this PR and the corresponding issues
• Automated (jest and/or cypress) tests added (for new features) or updated (for existing features)
• This PR requires manual testing

[mykeels]

Are all aliases relative to the project root directory?

[thekp]

Are all aliases relative to the project root directory?

Yes ^

@mykeels
The webpack aliases are relative to the root of Simorgh because of the functionality here: https://github.com/bbc/simorgh/pull/3707/files#diff-9aa58844b835b1672134e3b1a55da686R1-R9

The jest alias is also relative to the root because of the <rootDir> tag used.
jest doc:https://jestjs.io/docs/en/configuration#modulenamemapper-object-string-string

[dr3]

Missing alias usage in simorgh/src/app/routes/getInitialData/utils/getRouteProps/index.js 🙈

[dr3]

Checked tests, eslint, storybook. npm run dev and npm run build LGTM, great work

[FK78]