Fix floating point validation on Characteristic Set

[OrigamiDream]

♻️ Current situation

Related:

• Critical floating point error on Characteristic Set #955

💡 Proposed solution

The provided fp value must be same with the characteristic value.

Previously, this didn't work because of remainder between provided value and minimum step size.
Therefore, I suggest a new stable constant, epsilon, which is 1.
This patch fixes the issue by reducing remainder significantly.

The value of the constant is minimum.
It would crash plugins if the value is under 1.

⚙️ Release Notes

If your accessory have specific "level" of state, you can now change the ranges to 0~100%.
This makes your Siri reads the level of state properly.

➕ Additional Information

No additional information needed

Testing

"should validate Formats.FLOAT with precision with minimum steps" have been added in Characteristic.spec.ts#L1097

Reviewer Nudging

You don't need hard mathematical understanding!
You can just test it with eps = 0 or eps = 1.

[coveralls]

Pull Request Test Coverage Report for Build 2401686893

• 0 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 51.771%

---

Totals
Change from base Build 2243960438:	-0.05%
Covered Lines:	5712
Relevant Lines:	10070

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 2401686893

• 2 of 2 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.05%) to 51.771%

---

Totals
Change from base Build 2243960438:	-0.05%
Covered Lines:	5712
Relevant Lines:	10070

---

💛 - Coveralls

[Supereg]

Thanks for reporting and fixing this issue 🚀

[adriancable]

@Supereg - see my comments in #955. Unfortunately I think this was merged prematurely. This PR replaces a logic error in the rounding algorithm with another logic error.