Allow bypassing address validation in HT16K33 code to address Issue #1834

[chrisl8]

Allow adding an option called skipAddressValidation when calling the Led.Digits function to skip validating the given address and deleting them.

This will address Issue #1834

This allows using multiple HT16K33 devices on different external boards that might all be on the same address.

This is the only option I could come up with that I feel confident won't affect any existing code that may depend on the current functionality.

I've also added documentation for the option in the place that made the most sense to me.

Please let me know if you feel this option is reasonable, and if so, if I need to add any tests for this before acceptance.

[dtex]

My only concern is that this doesn't solve things for the auto-addressing of multiple HT16K33s across multiple boards.

What if we stored addresses in a WeakMap with boards as keys? It wouldn't require changes to the API, would still protect addresses from reuse, and support multiple boards.

[chrisl8]

My only concern is that this doesn't solve things for the auto-addressing of multiple HT16K33s across multiple boards.

I was just taking the "easy way out" with the assumption that I'm the only person on the planet even doing this, but my way definitely leaves users like me without that feature.

That feature seems a little odd to me, as I would expect anyone using multiple HT16K33s to already know their addresses, and want to address each one specifically rather than letting the code "guess" for them.

What if we stored addresses in a WeakMap with boards as keys? It wouldn't require changes to the API, would still protect addresses from reuse, and support multiple boards.

That sounds like a good idea to me. I can try to revisit this when I have free time again.