Builders management

[martinbonnin]

Description

Follow up from #3301, we should uniformize our Builder patterns. ApolloClient.Builder() especially has a bunch of Builder "shortcuts" that seemed interesting at first but end up creating issues:

• How to properly close shutdown an apollo client version 3? #3802
• Customizing your WebSocket protocol using GraphQLWsProtocol documentation  #6253
• Allow building an ApolloClient on top of another one changing the underlying OkHttpClient #3759

TODO:

• deprecate (and ultimately remove) the intermediate builders
• add ApolloClient.Builder.normalizedCacheInterceptor(), like there is retryInterceptor()
• add ApolloClient.Builder.httpCacheInterceptor(), like there is retryInterceptor()
• decide what to do with HttpNetworkTransport.newBuilder(). It could potentially be dangerous to create multiple instance sharing a single closeable resource. But it's possible anyways by reusing the original builder so we might as well decide to keep it with a bit warning.
• Add Kotlin builder-DSL helpers
• update docs

See #6287
See #6300