ideas to improve GitHub integration

[ocaisa]

Ideas to make --new-pr smarter:

• also support including patch files for easyconfig files (cfr. also include patch files in --new-pr and --update-pr #1852)
• also support removing (& renaming?) easyconfig files (handle deleted files in --new-pr #1853)
• automatically include any new easyconfig files for dependencies (just like --robot) (add support for combining --new-pr/--update-pr and --robot #1881)
• automatically include patch files is they're missing
• support creating PRs to easyblocks repo (--new-pr for easyblocks and framework #1876)
  • WIP at develop...boegel:new_pr_easyblocks_framework
• support creating PRs to framework repo (--new-pr for easyblocks and framework #1876)
• automatically clean up comments & build stats that were added to easyconfigs, in case the easyconfigs are being plucked from the archive
• support for --sync-pr, to (try to) sync a specific PR with current develop
  • this would require a proper way of dealing with merge conflicts (a simple solution would be to simple bail out and cancel the sync; another would be to print a list of files where conflicts need to be fixed in)
• support for --sync-pr-with-branch
• support for --merge-pr, to merge a specified PR, but only after running a couple of checks (e.g. target branch, code review (lgtm), successful test report, etc.)
  • this is already implemented in a stand-alone script, i.e. https://github.com/boegel/eb-scripts/blob/master/pr_check.py, but it should be integrated in eb
• support for --search-pr, for searching pull requests for updates of a particular software package (title-only (fast), or actual contents (slow))

[boegel]

@ocaisa I enhanced the description a bit, to include other ideas to make --new-pr smarter/better, and also made it a checklist...

Let's make this a project issue to track ideas/feature requests for --new-pr and --update-pr...

[boegel]

although not all boxes are checked here yet, the support for --new-pr and --update-pr is now considered stable (cfr. #1979)

the remaining things to implement will be enhancements to what is supported already, there should be no changes in semantics of the existing functionality of --new-pr and --update-pr

[boegel]

I've enhanced this a bit to include other ideas for improving the GitHub integration beyond --new-pr and --updat-pr.

[akesandgren]

Would be nice if --new-pr would automatically include any required patch files.