Add theme, router and current product, React Hooks and HOC to easily access the appropriate data

[devbucket]

Description

In order to easily create custom Routes and access the product data very easily, we added three new React Hooks:

• useTheme - Provides all theme components that are defined in the Theme API
• useRoute - Provides all route parameters that are useful for render controlling
• useCurrentProduct - Provides the current product context information on the Product Detail Page

Additionally all this information can be accessed with HOC:

• withTheme
• withRoute
• withCurrentProduct

Type of change

Please add an "x" into the option that is relevant:

• Bug Fix 🐛 (non-breaking change which fixes an issue)
• Enhancement 🚀 (non-breaking change which adds functionality)
• Breaking Change 💥 (fix or feature that would cause existing functionality to not work as expected)
• Polish 💅 (Just some cleanups)
• Internal 🏠 Only relates to internal processes.

[coveralls]

Pull Request Test Coverage Report for Build 2455

• 0 of 7 (0.0%) changed or added relevant lines in 3 files are covered.
• 5 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.05%) to 51.107%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
libraries/engage/core/hooks/useRoute.js	0	2	0.0%
libraries/engage/core/hooks/useTheme.js	0	2	0.0%
libraries/engage/core/hooks/useCurrentProduct.js	0	3	0.0%

Files with Coverage Reduction	New Missed Lines	%
libraries/common/helpers/portals/routePortals.js	5	0.0%

Totals
Change from base Build 2451:	-0.05%
Covered Lines:	5784
Relevant Lines:	10696

---

💛 - Coveralls

[fkloes]

I think, this PR doesn't cover the requirement from the story yet. Using both contexts is now really simplified, but one still needs to import and use them explicitly.

What about extending the default Route component with additional props to activate the context injection without importing extra stuff? We could also provide a new component.
I got some feedback from PS, that this could definitely improve the workshops, since they don't need to explain "new" terms like "HOD" or "Hooks".

[fkloes]

Why did you replace this line by commented out code? Is it just because externals are now supposed to use the hooks / HOC?
In the recently updated DevDocs we have some articles where import { Theme } from '@shopgate/engage/core'; is used within code snippets. This will not work anymore when the export is gone. So you also need to update the developer center articles with the new patterns from this PR.

[devbucket]

I actually talked that through with @sznowicki from PS and we confirmed that this will be the solution to go for.