Release 0.4.1

[magikh0e]

What

Cut the 0.5.0 release: version 0.5.0.dev1 -> 0.5.0 in __init__.py and pyproject.toml, and date the changelog [Unreleased] -> [0.5.0].

Why

#21 (device remembering) landed on master as 0.5.0.dev1. Publishing a 0.5.0 release pushes it to PyPI via python-publish.yml, which lets the Home Assistant integration require drone_mobile>=0.5.0 and ship the fix to HACS users.

After this merges, create a GitHub release tagged v0.5.0 to trigger the PyPI publish.

[magikh0e]

Note on the red CI here: it isn't from the version bump, it's the same ruff / black / stale-test failures that #24 fixes (they surfaced once #22 made the test suite run on master). Cleanest order is to merge #24 first so master goes green, then this branch just needs a rebase onto master to pick up the fixes and go green too. Happy to rebase it the moment #24 lands.

[bjhiltbrand]

Changed to release 0.4.1, as it didn't seem like a big enough revision to warrant a change to the next number (not that I have any real criteria for what constitutes a big enough revision, mainly just vibes).

[magikh0e]

Changed to release 0.4.1, as it didn't seem like a big enough revision to warrant a change to the next number (not that I have any real criteria for what constitutes a big enough revision, mainly just vibes).