feat!: rebuild as a tested BLE package and CLI

[ddtdanilo]

Summary

• replace duplicate scripts with an installable, typed ut383bt package and CLI
• add explicit BLE discovery and device selection; remove the committed personal peripheral UUID
• add resilient notification parsing, UTC measurement models, CSV logging, and guaranteed async cleanup
• update to Bleak 3 with explicit GATT write response behavior and Python 3.11-3.14 support
• add complete English README, architecture, API, observed-protocol, troubleshooting, privacy, security, support, contribution, citation, agent, and release documentation
• preserve the WTFPL Version 2 license declared by the original scripts
• add CI, CodeQL, dependency audit, release automation, Dependabot, ownership, and issue/PR templates

Validation

• Ruff lint passes
• Ruff format check passes
• 43 tests and 2 parameterized subtests pass without BLE hardware
• 97.98% branch coverage
• wheel and source distribution build successfully
• pip-audit reports no known vulnerabilities in auditable dependencies
• offline CLI parse and version smoke tests pass
• workflow, issue-form, Dependabot, and citation YAML parse successfully
• all GitHub Actions use immutable commit SHA pins
• git diff --check passes

Compatibility and privacy

• device identifiers are runtime-only and differ by platform
• live hardware is deliberately excluded from CI
• observed GATT details are documented as empirical, not vendor-guaranteed
• logs and raw Bluetooth diagnostics have explicit privacy guidance

This PR establishes v1.0.0.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.