Add support for reactive PubSub consumers

[jeremyg484]

Support for reactive consumers is added. This gives the ability to bind the received PubSub message as a reactive type
to the subscriber method's body parameter, and to return a reactive type to which the
framework will subscribe.

Message automatic and manual ack/nack are handled accordingly.

Docs are added for the added reactive support.

This resolves issue #945

[timyates]

Nice!

Some really nitpicky typographical suggestions (license year, avoid tabs, wildcard imports and kotlinification suggestion)

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarCloud.

[sdelamo]

please add tests to test-suite-groovy, test-suiteand test-suite-kotlin.

Right now the code there, which is the one shown in the docs is not tested.

[jeremyg484]

@sdelamo @timyates This is ready for a re-review with the added tests. CI looks to be failing ATM because it's taking too long to download the docker image being used in the test-suite tests. I'll try to get that sorted out, but if either of you already know the potential solution to it I'd welcome your suggestions.

[sdelamo]

@timyates please review this again

[timyates]

@sdelamo I am doing. I got the test-suite passing without timing out downloading the 1GB docker image

Graal is failing, and I'm not sure why...there's a discussion on Discord

[timyates]

Questions about excluding listeners in the suites

But thinking about it, I guess these were not executed before as there were no tests 🤔

I removed some semi-colons, and some sonar smells in a commit

[jeremyg484]

Questions about excluding listeners in the suites

But thinking about it, I guess these were not executed before as there were no tests 🤔

I removed some semi-colons, and some sonar smells in a commit

@timyates Thanks for the assist! Any ideas about the Graal error that's happening now?

As for the disabled beans, you are correct that those classes were never being executed prior. In all cases I had to disable them because the PubSub topics they are trying to subscribe to either haven't been configured to exist in the docker container yet, or they overlap with the listeners that are now being tested (can't have multiple methods for the same subscription).

[timyates]

Any ideas about the Graal error that's happening now?

There's a thread in discord, Graeme says it's being investigated

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

37.6% Coverage
0.0% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint