Add UUID support for ISOBlue2 boards #2
Description
Currently ISOBlue boards are identified by 3 digit numbers manually entered before the board image is complied. This is not desirable because it slows down deployment of new boards, could lead to conflicts if multiple boards are accidentally given the same number, and puts a hard cap of 1000 boards that can be created without conflicts
Boards should use a auto-generated UUID style identifier instead, which would alleviate these concerns
Effort required to make this change has not been determined
Additional considerations:
- Should a human-readable board nickname also be implemented? Currently the 3 digit number allows easy tracking of the boards by humans which would be lost by switching to UUIDs
- Is compile-time the appropriate time to determine this UUID?
- Should the UUID be allowed to be changed? Change in ownership of device, privacy concerns, etc might demand this