CI for merging main to dev after merge PR

[prrao87]

Workflow improvement

Sometimes, we have the need to push minor changes to the main branch from a working level branch (for e.g., typo or error fixes in the public docs page). However, in this case, the main branch goes out of sync with the dev branch over time, making more tedious when we want to publish docs for new releases (which requires a merge in the opposite direction, dev --> main).

To help with this, @mewim proposed a CI that does the following:

• If the merge PR originated from any branch other than dev, and the destination branch is main, an action would trigger a second PR from main to dev to reflect the changes on the dev branch as well.

This would help us keep important changes that directly get deployed on main on dev as well, reduce scope for discrepancies, and improve the productivity of the team.