@AutoConfigureHttpGraphQlTester should not trigger the configuration of mockMvc

[snicoll]

HttpGraphQlTesterAutoConfiguration requires a WebTestClient to be available. The client may be configured to bind to the application, mockMvc, or a running server.

Currently HttpGraphQlTesterAutoConfiguration enables the auto-configuration of MockMvc. This seems to be inconsistent with what we've done recently to make all that opt-in.

[wilkinsona]

I think @AutoConfigureMockMvc can be removed. A WebTestClient is required but that could be a MockMvc-based WebTestClient or a "proper" WebTestClient. WebTestClientAutoConfiguration is now capable of providing either of those. In the MockMvc case, it'll use the MockMvc bean if if's there, otherwise it'll create a MockMvc instance under the covers. In other words, you could use @AutoConfigureMockMvc with various attributes to take control of the underlying MockMvc instance but you don't have to. For similar reasons, I think MockMvcAutoConfiguration can now be removed from the afterName of HttpGraphQlTesterAutoConfiguration.