Remove panic path in write_register(), associated with potential incorrect register slicing

[tullom]

This pull request introduces several improvements and fixes to the project, focusing on error handling in the register interface, lint configuration, and CI workflow enhancements. The most significant changes are grouped below by theme.

Error Handling and Robustness:

• Added a new RegisterSizeError variant to the BQ25773Error enum and updated the async register write implementation in src/lib.rs to explicitly check buffer sizes and return this error if the data does not fit, instead of using debug_assert!. This improves runtime safety and error reporting. [1] [2] [3]
• Updated tests to allow clippy::unwrap_used, ensuring that test code does not fail linting due to unwrap usage.

Lint and Metadata Improvements:

• Refined Cargo.toml keywords to better reflect the crate’s scope, and updated clippy lint settings to use stricter enforcement (deny instead of forbid) and to add more lint categories for improved code quality. [1] [2]

Continuous Integration Enhancements:

• Enabled the semver job in the GitHub Actions workflow (.github/workflows/check.yml) to check for semantic versioning compatibility on each run, improving release safety.

[kurtjd]

Looks good, though this counts as a breaking change I believe since the BQ25773Error is not marked non_exhaustive.

[tullom]

Looks good, though this counts as a breaking change I believe since the BQ25773Error is not marked non_exhaustive.

I realized i never published this crate, so i added a commit here that enables the semver check. It will fail for now, but once i get 2 approvals, i will cargo publish and re-run CI and i should be able to merge then

[asasine]

non-blocking

Outdated