feat: Add priority to jahiaComponent

[baptistegrimaud]

Description

Add a new priority parameter when defining components (both views and templates) to decide which component should be used when rendering a given view/template, in case several components match a given resource.
The parameter is optional and its default value is 0. It can be set to a negative or a positive number.
The component with the highest priority has precedence over the other components.

NB: the identifiers of the registered components now include the priority, only if the priority is different from the default value (0), to remain backward compatible with JS modules that might have been deployed with a prior version of Javascript Modules Engine.

Checklist

Source code

• I've shared and documented any breaking change
• I've reviewed and updated the jahia-depends

Tests

• I've provided Unit and/or Integration Tests
• I've updated the parent issue with required manual validations

Tip

Documentation to guide the reviews: How to do a code review