Create a KeyPair service to handle general key management

This looks good. One naming nit in MR.

At this point, if people do not want to be dependent on phpseclib, they need to overwrite the key_asymmetric.key_pair service with their own, and they need to extend the KeyPair class because there is no interface yet.

Two separate areas of future extension:

1) so that other services don't need to extend KeyPair:

• define an interface
• make KeyPair implement the interface
• mention the interface (not KeyPair) in the constructor method signatures

2) If we want this to be code-free, i..e people just install another similar service that uses another library, and it (usually) gets picked up automatically, we need to make the current KeyPair service just one of potentially many, and

• give each service a applies(): bool method (our implementation being e.g. {return class_exists('phpseclib3\Crypt\PublicKeyLoader';}
• add an extra service (e.g. KeyPairManager) which is a service collector and also implements
  

  getKeyProperties() {
    foreach ($this->sortedKeypairProviders as $provider) {
      if ($provider->applies()) {
         return $provider->getKeyProperties();
      }
    }
    return some-default;
  }
  

• tag the current KeyPair service to be such a provider
• use the new KeyPairManager whereever we now use KeyPair, in our code.

Those can be later extensions, when this actually gets implemented by another service / needs to be swappable. Nothing in this issue stands in the way of it.

Needs Work for at least the proposed class name change. If you don't agree, you can merge.

> step 2, change the class implementation of KeyPair to replace phpseclib with base PHP OpenSSL calls

Ah. That makes a lot of sense (and cancels the need for all the things I just made up on the spot while reviewing).