There seemed to be a race condition between two different commits on the
same day, one of which renamed a method and the failure to call the
method was shadowed by a try-except. The result was that we couldn't run
the muxing integration tests.

We were using a handcrafted logic to determine if it was an exact
match or an extension match (sorry about that).

This PR replaces it for glob patterns

Bumps [litellm](https://github.com/BerriAI/litellm) from 1.61.20 to 1.62.1.
- [Release notes](https://github.com/BerriAI/litellm/releases)
- [Commits](https://github.com/BerriAI/litellm/commits)

---
updated-dependencies:
- dependency-name: litellm
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com>

* Disable suspicious commands for now
This is not quite the right place for the code check to go.

---------

Signed-off-by: nigel brown <nigel@stacklok.com>

* Added a class which performs semantic routing

Related to: #1055

For the current implementation of muxing we only need
to match a single Persona at a time. For example:
1. mux1 -> persona Architect -> openai o1
2. mux2 -> catch all -> openai gpt4o

In the above case we would only need to know if the request
matches the persona `Architect`. It's not needed to match
any extra personas even if they exist in DB.

This PR introduces what's necessary to do the above without
actually wiring in muxing rules. The PR:
- Creates the persona table in DB
- Adds methods to write and read to the new persona table
- Implements a function to check if a query matches to the specified persona

To check more about the personas and the queries please check the unit tests

* Attended PR comments

* Add a migration to update previous matchers to glob patterns

On #1193 we put in place code for using glob patterns in muxing.
This PR also updates the DB entries

* change in concat function to older version

* manually changed down revision on migration

I fount dumping requests and replies invaluable with debugging. But we
never enabled dumping the requests with copilot. Let's do it now!

* feat: remove not needed encryption of secrets

Instead use an uuid generator as we do for pii, and reuse
same session store mechanism

Closes: #929

* fix tests

* unify interface in sensitive data

* add missing tests

* changes from rebase

* fixes from review

* fixes in tests

* fix tests