fix: convert run_seconds float values to int before API calls

[JoshDev]

Summary

Converts float values in run_seconds to integers before sending to the OpenSprinkler API.

Problem

OpenSprinkler interprets decimal points as zone separators, so values like [0, 480.0, 540.0] fail while [0, 480, 540] works correctly. This commonly occurs when users calculate run times using templates that produce float results.

Solution

Added int() conversion in all code paths that pass run_seconds to the API:

1. Dict-based run_seconds - Convert values when building the list
2. Config objects list - Convert values when building the list
3. Direct list - Convert with list comprehension [int(s) for s in run_seconds]
4. Individual station run - Accept float type and convert to int (previously raised exception)

Testing

Added pytest test suite with 8 tests covering:

• Float list conversion (main issue case)
• Dict value conversion
• Mixed int/float conversion
• Backwards compatibility with int values
• Single station float handling
• None and invalid type handling

All tests pass locally.

Fixes #294

[vinteo]

Thanks for adding tests, would it be difficult to add a github action to run the tests?

[JoshDev]

Added a GitHub Actions workflow to run the tests! It runs pytest against Python 3.12 and 3.13 on every push and PR.

Also cleaned up unused imports in the test file.

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[vinteo]

Thank you very much