New Module Hooks API

[filrak]

Related issues

Short description and why it's useful

This change is meant to prevent future problems with before/after registration hooks in modules. Grouping it into one object allows much easier modifications and future extending than relying on params order. it's the very same approach that nuxt is using with their modules.

TODO:

• Changelog

(describe in a few words what is this Pull Request changing and why it's useful)

Screenshots of visual changes before/after (if there are any)

Screenshot of passed e2e tests (if you are using our standard setup as a backend)

Upgrade Notes and Changelog

• No upgrade steps required (100% backward compatibility)
• I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

Contribution and currently important rules acceptance

• I read and followed contribution rules
• I read the TypeScript Action Plan and adjusted my PR according to it
• I read about Vue Storefront Modules and I am aware that every new feature should be a module

[pkarw]

It's way better to pass the VSF object because it will allow us to extend before and after hooks without changing the definitions.

However, there are currently some modules on Github created with the previous approach so we should be compatible with it (I mean with passing Vue, config .. as separate arguments). Would it be possible?

[filrak]

@pkarw i already spoke with extension devs and will propose a proper PRs to their repos ;)

[patzick]

i think this is good move:)

please remove also added storefront-ui reference, this shouldn't be added here