Add OpenRC service backend

[Pectics]

Context

Roadmap item imported from PLAN_REQUEST.md and PLAN_RESPONSE.md for v1.1+ — Post-v1 Backlog.

Upstream references

• [Feature]: OpenRC support spencerwooo/mihoro#180

Upstream decision

• Ported
• Reimplemented
• Deferred
• Rejected

Reason: Deferred until after v1.0 because it expands the service-backend matrix.

Scope

• Evaluate OpenRC service lifecycle after systemd backend stabilizes.
• Design backend extension and add OpenRC integration tests before declaring support.

Acceptance criteria

• The scope above is implemented or documented in issue-linked PRs.
• Relevant upstream references are reviewed before implementation starts.
• Tests are added, or the PR explicitly explains why this is documentation-only.
• Documentation is updated, or the PR explicitly explains why no docs changed.
• Migration impact, security impact, and rollback behavior are evaluated.

Out of scope

• Work explicitly listed outside v1.0 in the roadmap remains deferred unless this issue is in v1.1+ — Post-v1 Backlog.
• No GitHub Project board, branch protection change, local commit, or repository file edit is part of this import pass.

Dependencies

• Depends on Introduce persisted systemd-user and systemd-system backends #12
• Depends on Publish supported distributions and systemd compatibility matrix #29

Security and rollback considerations

Apply Mihoto's safety rule for this issue: updates, migrations, service changes, TUN/DNS changes, and credential handling must be explicit, validated, auditable, and recoverable. Secrets and subscription URLs must be redacted from logs and issue artifacts.