Device ID for OWL1 on new firmware

[antisvin]

FW side update for RebelTechnology/OwlProgram#70

[pingdynasty]

If the patch needs to know what firmware is used then it's probably better to add a firmware identifier.
What is the requirement for this?

[antisvin]

What is the requirement for this?

This is explained in linked issue to OwlProgram repo. But the general goals here are to allow building patches that would either:

1. Support both firmwares with corrert ADC inverting behavior in patches

2. Only support new FW and don't perform any unnecessary compatibility checks

We could keep using first option in web patcher, but suggest users with legacy FW to switch to new FW and their patches would still have correct behavior. And second option would be used by anyone building patches offline with new FW.

Adding FW ID looks like a cleaner solution for first option. But it seems to be more invasive - I guess it would require using a different program vector version?

[antisvin]

This was done without merging current PR