Account auto-negotiation kicks in before configuration from config server is applied

[snicoll]

If you have configured an existing account (api token) using Spring Cloud's config server, the starter attempts to auto-negotiate an account anyway.

It looks like the configuration from the config server is not available when EnvironmentPostProcessor runs.

[snicoll]

Actually, this is not a bug here but a limitation of Spring Cloud Server that is mutating the environment at the wrong phase, see spring-cloud/spring-cloud-commons#608.

I've asked if a reasonable workaround exists and we'll apply it here accordingly.

[snicoll]

Unfortunately, I don't think that's reasonable to move the logic elsewhere just for config server. In the meantime I've added support for checking if wavefront.freemium-account is set, see #48.

If that property is set to false alongside the api-token, things will work as expected.