Allow automerge for version or migrations only

[CJ-Wright]

Note that this will need a PR in webservices to make the most of this and some advertising.

The hope here is that ABI migration PRs are more likely to break if there are any changes that need to be applied to the feedstock. Enabling migration automerge will greatly speed up uptake of pins, similar to the R 4.0 migration.

@beckermr @isuruf @scopatz

[codecov]

Codecov Report

Merging #1063 into master will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master    #1063   +/-   ##
=======================================
  Coverage   57.44%   57.44%           
=======================================
  Files          53       53           
  Lines        5087     5087           
=======================================
  Hits         2922     2922           
  Misses       2165     2165           

Impacted Files	Coverage Δ
conda_forge_tick/migrators/migration_yaml.py	64.32% <ø> (ø)
conda_forge_tick/migrators/version.py	79.50% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 37b9502...b46dbb7. Read the comment docs.

[beckermr]

IDK what the webservices has to do with this. Do you mean a PR in the automerge action code?

[CJ-Wright]

Don't we have a admin command to add automerge keys to the conda-forge.yml?

[beckermr]

Yes. Did you want variations of that command?

[CJ-Wright]

I think that would be awesome! Unless we're interested in setting the default to automerge for migrations only