Disable in-process transport by default and add @AutoConfigureInProcessTransport annotation

[panic08]

Here I have added the AutoConfigureInProcessTransport annotation which should be set over the test where we want in-process transport to be enabled. I also added the class InProcessTransportEnvironmentPostProcessor which implements EnvironmentPostProcessor and where I use AnnotationUtils.findAnnotation to check if the startup class is marked with an annotation or not. If yes, then we need to enable in-process transport and we set spring.grpc.inprocess.enabled=true. I also set matchIfMissing to false in InProcessGrpcServerFactoryAutoConfiguration (ignored as it is by default) so that in-process will default to false.

Closes #77

[dsyer]

I'm not sure this is going to work. Don't we need something that is aware of the test environment? Look at the existing @AutoConfigure* annotations to see how they are implemented.

[panic08]

Thanks so much for the tip. I've looked into it more, tested it, and I'd like to say. Could we create an InProcessFactory that will implement ContextCustomizerFactory? That is, make a class like ObservabilityContextCustomizerFactory

[panic08]

I listened to what you said. For an idea for looking at @AutoConfigure* annotation implementations, I decided to go with AutoConfigureObservability as advised by @onobc .

I created an InProcessTransportContextCustomizerFactory that will check for the presence of the @AutoConfigureInProcessTransport annotation I created. If this annotation is not present, I've added the ability for properties to specify spring.grpc.inprocess.auto-configure to enable auto-configuration (I think this will be good for us?). If auto-configure is enabled, for now we only do one thing, in the test properties set spring.grpc.inprocess.enabled=true

[dsyer]

I took a version of your PR from yesterday and added some extra code to detect if we are running in a test. I think this works now. Merged in e0a744b. Thank you.