Fixed behaviour for refresh

Re-check connected clients immediately after a reload

A reload rebuilt the known set but did not re-evaluate anything, so a
device it had just forgotten stayed silent until the next WebSocket
event or fallback poll. With FALLBACK_INTERVAL at 600 and the device
already connected (so producing no events), that meant up to ten minutes
of apparent silence after /reload fresh discarded an allow.

Adds a dedicated recheckCh rather than reusing trigger, which runs the
WebSocket delay and IP-wait and would label the check as WebSocket
sourced. The send is non-blocking, so a reload cannot stall the loop when
a check is already queued.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QSwZJ6jnJ8Gs8mLLkx2mHY

Added reload

Add /reload fresh to rebuild from the file alone

Plain /reload rebuilds the known set from KNOWN_MACS_FILE unioned with
the database, so allow decisions made from the buttons are kept. That is
the right default: silently discarding them would make "Allow
permanently" mean only "until the next reload".

/reload fresh empties the database first, making the file the sole
source of truth. It reports how many stored allows were discarded, and
an unrecognised argument returns usage rather than falling back to
either behaviour, since the two differ in whether data is destroyed.

Slash command arguments now travel on Command.Arg, decoded from the
"text" field of the slash_commands payload.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QSwZJ6jnJ8Gs8mLLkx2mHY

Merged wiht upstream added slack interactive mode

CI: fix release builds producing zero tags

A release build failed with "tag is needed when pushing to registry"
because metadata-action emitted no tags at all:

- type=semver silently produces nothing for a tag without a patch
  component, e.g. "v2.0" (logged only as a warning).
- latest was gated on is_default_branch, which is false for a release
  since it builds from a tag ref. Deployments pinned to :latest would
  never have been updated even on a successful build.

Adds type=ref,event=tag as a safety net so any tag always yields at
least one image tag, and keys latest off the event instead.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QSwZJ6jnJ8Gs8mLLkx2mHY

Merged wiht upstream added slack interactive mode

Full Changelog: https://github.com/rcastberg/UnifiClientCheck-Docker/commits/v2.0

Small fixes

Added ip source, none notifer

First test CR publish

Full Changelog: https://github.com/rcastberg/UnifiClientCheck-Docker/commits/v0.01