patch release, consider including azure-resourcemanager into patch_release_candidate.txt

Current release cycle between ARM and BOM is:
patch release -> azure-resourcemanager release -> BOM release. This is due to the peculiarity of azure-resourcemanager library:
- it's an umbrella library around 20+ premium libraries and released **monthly**
- each of the underlying premium library release is **not** controlled by us, but rather, service teams
- if any of the underlying premium library is released, next release of the azure-resourcemanager release should at least be `minor`, not `patch`
Thus, if we don't make changes to current patch-release procedure, azure-resourcemanager library cannot be patch-release candidate.

Time window of patch release and BOM release is usually 1 day, leaving little release window for azure-resourcemanager.

Considering adding azure-resourcemanager into patch_release_candidate.txt, letting patch-release patch azure-resourcemanager.