allow the option to use an external pool in MessageDispatcher

[damcaoson]

Hi, as the title suggests, it would be helpful if the MessageDispatcher could take an external pool as a parameter, instead of always using the static pool. This is especially useful in parallel messaging situations, as I mentioned in #120.

[davebaol]

Looks good to me. Only I don't like upper case letters for member variable POOL.

[damcaoson]

I don't prefer the uppercase POOL either. I left it unchanged because I didn't want to alter the git annotation for such a small change. But since you don't like it, I'll update it to lowercase.

[davebaol]

@damcaoson Thanks

@Tom-Ski or any other maintainer. I cannot remember where the build server is. So please, send me this info or merge this PR yourself if the remote build succeeds. Thanks 😄

[Tom-Ski]

@davebaol think we will migrate this to GHA, because we are doing that everywhere else.

[Tom-Ski]

@davebaol ok it should be setup now. Snapshots are deploying on commits to master. GH release is tied to a real maven release, so you can trigger it from here by making a new release on GH. (Version info is now in gradle.properties, so thats where you increment)

Also added auto running on PR's so it will build and also run your unit test suite. Let me know if any issues!

[davebaol]

@Tom-Ski Great, thanks.