Fix logging flow rules

[rak-phillip]

Summary

This resolves an issue with adding a include / exclude pod card to the list when creating a new flow for the logging chart.

Fixes #11933

Occurred changes and/or fixed issues

• replace set() usage with assignment
• create a new array to ensure that reactivity is triggered for matches

Technical notes summary

We encountered a similar issue related to using push that was resolved in #11788

• https://github.com/rancher/dashboard/pull/11788/files#diff-ac9d14c56bc5c1631a8b0bb855b7d34cb69d9d1be89f1c3b72c31f03381939f7R160

Areas or cases that should be tested

• Logging (see issue description)

Areas which could experience regressions

• Logging (see issue description)

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes