introduce project specific elpy-rpc processes

when elpy-rpc-ensure-open in a new buffer is used:
- if there is an RPC process associated with the project, use that one
- if elpy-rpc-project-specific is:
  + nil : the project is associated with the global RPC process
          (which is started, if necessary), (default)
  + ask : if the users answers yes to a prompt, start a project-specific
          RPC process and associate it with the current project
  + t   : start a project-specific RPC process and associate it

at any point a project-specific RPC process can be started and
associated with all buffers belonging to the current project by
invoking elpy-rpc-open-project-specific.

elpy-rpc-pool-gc kills unused rpc buffers.

(Small modifications to the patch done by Jorgen Schaefer)
elpy-rpc-project-specific: Remove the 'ask option.

This was very annoying, as the RPC process is not even started
when the buffer is opened. Suddenly, a prompt would show up. So
I changed my mind on the usefulness of this option. People who want
the 'ask behavior can set the value to nil and simply run
`M-x elpy-rpc-open-project-specific` when they want a project-specific
Elpy.

`elpy-rpc-pool-open` adjusted accordingly.