[PROPOSAL] Rename repository to gateway_provisioners

[kevin-bates]

As some of you know, I'm not happy with the name remote_provisioners for the following reason: It's way too generic. Other folks may want to create their own sets of provisioners that happen to work remotely and I feel this repo will be the target of such confusion. I'd rather not "steal the name", nor do I think any repo should be named remote_provisioners for the same reason.

I believe the name gateway_provisioners includes both history and relevance. While it's true that you do not need a gateway server to host remote provisioners, it's very likely the case that you will. This is because these provisioners essentially require the invoker to be on the same network as where the kernel will run. As a result, many folks will need to "hop through" a gateway server that has been provisioned relative to the target network. Yes, applications like Jupyter Hub that spawn notebook servers in Kubernetes, will not require a gateway server but many others will want to deploy a gateway server in the cloud, in which case, Gateway Provisioners would be handy.

By changing to Gateway Provisioners, we also imply a well-known family of provisioners, all of which happen to be remote (for now), but perhaps not always.