Allow running integration tests in Non-Production pipelines - Status changed to: Investigating

[#1]

Request for Feature Enhancement (RFE) Summary:	Integration tests and UI tests are executed automatically on the Stage environment as part of a Production pipeline. We would like to run our integration tests earlier, when pushing code to one of our Development environments. This would allow us to catch bugs early without risking the timeline of Production deployment.
Use-case:	We have two Development environments. One receives the latest code, another is used as a stabilization/bugfixing environment before a Production release. We would like to run our integration tests on the stabilization environment to catch issues early.
Current/Experienced Behavior:	Integration tests can only be executed against the Stage environment, as part of a Production pipeline.
Improved/Expected Behavior:	Integration tests can be executed against a Non-Production pipeline. This could be another toggle in the UI, in addition to the Deployment Trigger and Important Metric Failures Behavior toggles.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as a Cloud Service
Customer-name/Organization name:	NI
Screenshot (if applicable):	N/A
Code package (if applicable):	N/A

[#2]

@csaba_varga 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference CMGR-38707. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.