Updating expeditor configuration

[jayashrig158]

Signed-off-by: jayashri garud jgarud@msystechnologies.com

Description

i) The merge_actions subscription shortcut has been deprecated. All subscriptions should be declared via the subscriptions block for clarity. ii) Release branches are a first-class concept in Expeditor, and should be represented as such. iii) The {{agent_id}} format is changing such that it is no longer a viable variable for the pullrequest* event subscriptions.

Related Issue

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New content (non-breaking change)
• [ ] Breaking change (a content change which would break existing functionality or processes)

Checklist:

• [ ] I have read the CONTRIBUTING document.

[chef-expeditor[bot]]

Hello jayashrig158! Thanks for the pull request!

Here is what will happen next:

1. Your PR will be reviewed by the maintainers.
2. Possible Outcomes a. If everything looks good, one of them will approve it, and your PR will be merged. b. The maintainer may request follow-on work (e.g. code fix, linting, etc). We would encourage you to address this work in 2-3 business days to keep the conversation going and to get your contribution in sooner. c. Cases exist where a PR is neither aligned to Chef InSpec's product roadmap, or something the team can own or maintain long-term. In these cases, the maintainer will provide justification and close out the PR.

Thank you for contributing!