Use rpc to check if larger temp range can be used

[nickolas-deboom]

Type of Change

• [ ] WWST Certification Request
  • If this is your first time contributing code:
    • [ ] I have reviewed the README.md file
    • [ ] I have reviewed the CODE_OF_CONDUCT.md file
    • [ ] I have signed the CLA
  • [ ] I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com
• [ ] Bug fix
• [x] New feature
• [ ] Refactor

Checklist

• [x] I have performed a self-review of my code
• [x] I have commented my code in hard-to-understand areas
• [ ] I have verified my changes by testing with a device or have communicated a plan for testing
• [x] I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change

CHAD-14205

For RPC version >= 6, the edge drivers can always assume that temperature values received from the setTemperatureSetpoint command are in Celsius. We can therefore allow a larger range for setpoint values in the driver, because we no longer need to be concerned about the Celsius and Fahrenheit scales overlapping. This PR introduces new limits depending on the RPC version, which are larger than the current ranges, but still limit the setpoint range values as a type of "sanity check" on the values received from the device (sometimes the values from the device are not set, or are not reasonable). Please offer any feedback if you have any opinions on different values that should be used for each device type.

Summary of Completed Tests

See new unit tests.