fix: preserve tag filters during procedure batch expansion

[mvanhorn]

Update each Procedure batch match arm to pass the request's tags into the shared expansion helper along with its pattern. Make the helper build the same tag-aware ResourceQuery used by direct batch execution, loading the tag catalog only when a non-empty filter must be resolved and retaining the existing no-filter behavior for an empty list. Procedure stages expand batch executions into individual executions before running them. That expansion currently forwards each batch request's pattern but replaces its resource query with the default, so tags are discarded and stacks outside the requested tag set can be selected.

A Procedure BatchPullStack execution with pattern * and tag auto-pull expands only stacks carrying auto-pull, excluding a stack tagged only local-build; A Procedure batch execution with multiple requested tags preserves the default all-tags matching behavior instead of dropping or weakening the filter.

Closes #1596