Allow using SocketAddress proxies instead of just InetSocketAddress

[AlexProgrammerDE]

This commit adds new socketAddress methods and tries to keep backwards compat for users using the old address methods, which are deprecated. I'd recommend removing socketAddress and renaming it back to address on the next major release.

Fixes #3242

[AlexProgrammerDE]

I guess the error lies in that new methods to the interface were added?

[AlexProgrammerDE]

Maybe this can be fixed by keeping address unimplemented and the socketAddress method defaulting to delegating to address. And then the implementing builder class overrides socketAddress and implements address as the one delegating to socketAddress. Seems a bit unnecessary though since this class is only supposed to be implemented by the builder class.

[violetagg]

what do you think about this?

		default Builder socketAddress(SocketAddress address) {
			throw new UnsupportedOperationException();
		}

		default Builder socketAddress(Supplier<? extends SocketAddress> addressSupplier) {
			throw new UnsupportedOperationException();
		}

[AlexProgrammerDE]

Sure, lets do it

[AlexProgrammerDE]

Should pass checks now and is ready for review.

[AlexProgrammerDE]

It seems like the build failed because of unrelated reasons with ssl stuff on windows. I've merged now upstream into my branch and I hope the build passes now.

[AlexProgrammerDE]

Seems like a request failure to maven central broke the build this time:

Maybe try rerunning that failed test.

[AlexProgrammerDE]

Seems like there are still errors that aren't maven central connection issues. I doubt they are related to the content of this PR though.

[violetagg]

Failed tests on Mac OS CI are not related

[violetagg]

@AlexProgrammerDE Thanks for the PR!

@reactor/netty-team PTAL

[pderop]

@AlexProgrammerDE

Nice, thanks for the PR!

+1