Bridge subscription failure will cause a disconnect

[abiliojr]

Currently, bridged connections will silently ignore subscription errors. This PR changes that by forcing the bridge to reconnect whenever a failure is received in the SUBACK. The hope is that the failure is temporary, and that retrying will solve it.

The MR is composed of 4 commits. The first two add the basic functionality and test it. The last two make it optional (enabled by default).

Though a change in behavior, I suggest that by default a failure should cause a disconnect. A silent failure causes more trouble than it solves. If you disagree, please edit the commit and change it to false.

If you consider that giving the user the option is not needed, just discard the last 2 commits.

• Have you signed the Eclipse Contributor Agreement, using the same email address as you used in your commits?
• Do each of your commits have a "Signed-off-by" line, with the correct email address? Use "git commit -s" to generate this line for you.
• If you are contributing a new feature, is your work based off the develop branch?
• If you are contributing a bugfix, is your work based off the fixes branch?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you successfully run make test with your changes locally?

---