Release PP365 in different channels

[pzljanb]

Is your feature request related to a problem? Please describe.
Users are not able to install a new release of PP365 to test it in an existing environment in a good way.
Resources in the AppCatalog is shared between installations within the same tenant and does not support multiple versions to be installed.

Describe the solution you'd like
PP365 solution to be released in different channels (dev, beta, prod e.g.)
For this to work it's necessary to separate the resources used within the solution to make sure it does not interfere with different versions/ channels.

Resources affected:

• Webparts e.g. in the AppCatalog

These must be duplicated

• Termstore elments

These could be considered to be kept common in the first iteration

There is 2 different solutions (at least?) that could be considered to make this happen:

1. Call to resources in AppCatalog to be made based on the installations current channel ID

To get this to work the code must check which channel it is on and call the ID based on this
The code keeps info on all different AppCatalog IDs in this scenario

2. Swop reference to AppCatalog resources in the code when moving to the next channel (preferred?)

For this solution to work the ID used to call AppCatalog resources must be replaced thru the codebase each time the code goes to the next channel.

Additional context
A solution like this would make user organizations of PP365 able to install and test the next release before upgrade PROD environment.

Is this something your organization is willing to contribute to financially?