Remove rules associated with the auto-merge label

[mkArtakMSFT]

This label has been removed as part of the effort to clean-up the labels in the repo. So these rules don't work anymore. During the conversation with some team members, it sounded like the current behavior is preferable.

[ghost]

Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at.

[joperezr]

Not exactly related but what about [Infrastructure PRs] Add area-infrastructure label to dependency update Pull Requests Rule? I noticed it is approving the PRs as well, should we remove that action?

[joperezr]

Same question for task [Infrastructure PRs] Add area-infrastructure label to auto-merge Pull Requests

[joperezr]

Left a small question regarding two other tasks, but otherwise this looks good, thanks @mkArtakMSFT!

[mkArtakMSFT]

Not exactly related but what about [Infrastructure PRs] Add area-infrastructure label to dependency update Pull Requests Rule? I noticed it is approving the PRs as well, should we remove that action?

There was a reason we did this in the first place. Do we have reasons to believe that we should back up on this decision?
@wtgodbe what do you think?

[joperezr]

I'm assuming the reason might have been that in order for dependency flow PRs to get auto merged they required an approval? If that's the case, now that we are removing the auto-merge capability for those, then it probably makes sense to also remove the auto-approval.

[mkArtakMSFT]

Let's see what @wtgodbe has to say about this.

[wtgodbe]

I think it's fine to keep the auto-approval, that keeps the build-ops person's task more mechanical (check the PR is green, merge the PR). And I like keeping the auto-label for them too, it's accurate.

[mkArtakMSFT]

@joperezr I'm merging this change as is. I'm happy to continue the conversation and if we decide that more rules should be removed, I'd send another PR out.