Make "Mark all as resolved" on pending retries honor the period filter and selected queue

[johnsimons]

resolveAll sent a fixed epoch-to-now range to pendingretries/resolve, ignoring both the period filter and the selected queue, even though the toast tells the user "All filtered messages were marked as resolved". It now recomputes the date range from the selected period at click time, and when a queue is selected it PATCHes pendingretries/queues/resolve with the queue address, the same way retryAll works after #3142 and the same way the old AngularJS markAsResolvedAllMessages behaved before the Vue migration. Without a queue it still uses pendingretries/resolve, since "Mark all as resolved" is not gated on a queue the way "Retry all" is.

One behavior change to be aware of: with the default "All Pending Retries" period, resolve-all now covers the last 365 days, which is the same window the list itself shows for that option, instead of everything since 1970.

This also replaces the magic "empty" sentinel on selectedQueue with ref<string | null>(null). The type now carries the "no queue selected" state and the compiler enforces the null checks in the store and the view, and the placeholder option binds :value="null" so the dropdown behaves as before.

New driver tests in resolving-all-pending-retries.spec.ts cover the three paths: the default period requests the full window up to now with no queue address, "Retried in the last 2 Hours" narrows the range to two hours, and a selected queue routes to pendingretries/queues/resolve with the queue address and the displayed period. The test bed from #3142 now also captures resolve requests, ignoring the uniquemessageids body shape so resolving individually selected messages does not pollute the capture.

Reviewer Checklist

• Components are broken down into sensible and maintainable sub-components.
• Styles are scoped to the component using it. If multiple components need to share CSS, then a .css file is created containing the shared CSS and imported into component scoped style sections.
• Naming is consistent with existing code, and adequately describes the component or function being introduced
• Only functions utilizing Vue state or lifecycle hooks are named as composables (i.e. starting with 'use');
• No module-level state is being introduced. If so, request the PR author to move the state to the corresponding Pinia store.