fix(topics): honor wildcard flag during matching

[Abdulmumin1]

summary

​
makes TOPICS_ALLOW_WILDCARDS apply during topic matching, not only validation.
​
when the flag is disabled:
​

• persisted wildcard patterns like user.* are ignored during delivery matching
• exact topic subscriptions continue to work
• the standalone * still means subscribe to all topics
• stored wildcard topics are left untouched, so re-enabling the flag restores them
  ​
  this also applies to destination filtering, direct destination publishes, and manual retries.
  ​
  closes TOPICS_ALLOW_WILDCARDS: disabling the flag leaves existing wildcard subscriptions half-working #991

[alexbouchardd]

That should also impact the destination and tenant object responses and in the postprocess trim out the no longer valid wildcard topics

[Abdulmumin1]

That should also impact the destination and tenant object responses and in the postprocess trim out the no longer valid wildcard topics

like before returning the object through the API, remove embedded wildcard topics such as user.* when the flag is disabled.

for example, storage contains:

["user.*", "order.created"]

with the flag disabled, the API return just:

["order.created"]

[alexbouchardd]

Yes, otherwise the data is misrepresentative of the behavior and breaks the portal UI!