Fix monitor exclusion not being applied for newly detected nodes

[KiKoS0]

Closes #388

Summary

Fixes a small copy-paste typo making the monitor_excludes option not being used at all and the monitor_includes option being wrongly used in the Ring router to exclude newly detected nodes instead.

Details

I was having the same issue of what #388 is describing and noticed that it was caused by remote accessing nodes. When a remote shell connects to an app's node, it doesn't get excluded by the default monitor exclusions defined in:

cachex/lib/cachex/router/ring.ex

Lines 98 to 102 in e1278ac

	monitor_excludes =
	Options.get(options, :monitor_excludes, &is_list/1, [
	~r/^remsh.*$/,
	~r/^rem-.*$/
	])

You can see that the rem- values are showing up in this comment when calling Cachex.Router.connected()

iex(core@10.244.1.158)3> Cachex.Router.connected()
[:"[email protected]", :"[email protected]", :"[email protected]"]

iex(core@10.244.2.34)15> Cachex.Router.connected()
[:"[email protected]", :"[email protected]", :"[email protected]"]

[whitfin]

Hi @KiKoS0!

Awesome find, thank you so much for taking the time to look into it. I'll double check the CI/CD runs, and assuming it's all good I'll push this out immediately as a patch!