Add more gap between the orders of CloudFoundryVcapEnvironmentPostProcessor and ConfigDataEnvironmentPostProcessor

[kvmw]

CloudFoundryVcapEnvironmentPostProcessor's order is set to ConfigDataEnvironmentPostProcessor.ORDER - 1 to give it higher priority. These consecutive numbers ( N and N - 1 ) makes it impossible to register any other EnvironmentPostProcessor between them. Setting a bigger gap between two orders ( e.g. N and N - 5) fixes the issue.

[wilkinsona]

The earliest we could do this would be in a new minor release. Even that may be too soon as it could break backwards compatibility in a way that's hard to work around. I think we'll need to discuss our options here, perhaps we'll need an escape hatch that allows the old order to be reinstated.

[philwebb]

We talked about this and we're going to move the order of CloudFoundryVcapEnvironmentPostProcessor in 3.3. This seems like the least risky class to change.