fix: Updating tour feature to store wildcard path instead of the url path

[kristenarmes]

Signed-off-by: Kristen Armes [email protected]

Summary of Changes

Previously, if you configured a product/feature tour by using a wildcard path, the actual path of the page you visited would be stored rather than with the wildcard. This resulted in the tour showing up for every new page you visited under the wildcard. This change stores the actual configured path so that if wildcards are used, it will only show the tour on the first page you visit.

Tests

Updated tests to handle the change to the return value of getProductToursFor

Documentation

N/A

CheckList

Make sure you have checked all steps below to ensure a timely review.

• PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.
• PR includes a summary of changes.
• PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does

[Golodhros]

LGTM

Thanks for the fix!