[CI Platform] Enabled module publishing from feature branch prerelease publishing without publishing stable version

[ahmadabdalla]

Description

Allowed filtering for the modules to be published to only include prerelease version if the feature branch is not Main/Master.

What was happening is that if I want to deploy the module pipeline for the first time and I am on a feature branch, if I attempt to publish into TS/BR/AzArtifacts, then it will publish stable versions along side the preview version. This should not happen as the branch is not main.

Also updated the set readme where [1] split filter was causing issues in the customer environment. Made it [-1] to align with other split filters in the script, as we always want to take the last element from the filter.

Finally, added warning if the profile is not loaded. This scenario happens when self-hosted agents are used, and causes random profile load failures.

Pipeline references

Pipeline

Type of Change

• Bugfix (non-breaking change which fixes an issue)

Screenshots from ADO and GH for scenarios on feature branch and on main

Feature Branch

GitHub Actions

Azure DevOps

Main Branch

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• My corresponding pipelines / checks run clean and green without any errors or warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (readme)
• I did format my code