Make backports individually configurable or spread functionality across multiple modules.

I propose that this module be discontinued in favour of individual modules for each piece of backported functionality.

Some reasons for this are (probably not an exhaustive list):

• Having one "Backports" module that has a bunch of potentially unrelated things smooshed into one module is not a good idea. Why do I want to install one big module that provides heaps of things I don't want just for one thing I do want.
• It hinders discoverability. This is somewhat related to the previous point, because when searching for a specific functionality it is easier to find if the module is named after that functionality. (It is also better for finding modules on your file system once they are installed.)
• A Drupal 8 backports module sounds like it would provide all drupal 8 back ports, which this doesn't and is unlikely to ever due to many different developers creating backport modules of their own.
• If it does end up having a large number of different backports it will require more maintainer time so it would be better if different individual features had their own modules with their own maintainers so there is less risk of unmaintained features.

A potential argument for having them all together is that having a large number is very small modules is not a great idea either.

I think it is less of a problem though than having the meta module, because:

• People aren't likely to install all the backport modules as they likely will only need a couple of them.
• Having a couple of extra modules that potentially aren't even running code on most pages is not really much of a performance issue and if you need to squeeze every last bit of performance you are probably willing to make some customisations of your own anyway.
• If there are a few small backports that are all related to one feature then it may be preferable to put them together into one module, whcih would be perfectly acceptable.

A few examples of other backport modules that already exist are:
https://www.drupal.org/project/telephone →
https://www.drupal.org/project/escape_admin →
https://www.drupal.org/project/classloader →

Keeping the project page with a bunch of links to other backport modules is also not a good idea in my opinion as it is likely to get out of date easily.

We would be better off with a documentation wiki page with a list of back port modules.