Fix #833 - Failing test due to querystring order.

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>

)

Source-Link: googleapis/synthtool@d6103f4
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:39f0f3f2be02ef036e297e376fe3b6256775576da8a6ccb1d5eeb80f4c8bf8fb

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

* chore: Update CODEOWNERS

updating codeowners to allow reviews from partner team

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

…#834)

Co-authored-by: Anthonios Partheniou <partheniou@google.com>

Source-Link: googleapis/synthtool@dede53f
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-python:latest@sha256:fac304457974bb530cc5396abd4ab25d26a469cd3bc97cbfb18c8d4324c584eb

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>

This PR contains the following updates:

| Package | Change |
[Age](https://docs.renovatebot.com/merge-confidence/) |
[Confidence](https://docs.renovatebot.com/merge-confidence/) |
|---|---|---|---|
| [pyparsing](https://redirect.github.com/pyparsing/pyparsing) |
`==3.2.5` → `==3.3.2` |
![age](https://developer.mend.io/api/mc/badges/age/pypi/pyparsing/3.3.2?slim=true)
|
![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pyparsing/3.2.5/3.3.2?slim=true)
|

---

### Release Notes

<details>
<summary>pyparsing/pyparsing (pyparsing)</summary>

###
[`v3.3.2`](https://redirect.github.com/pyparsing/pyparsing/blob/HEAD/CHANGES#Version-332---January-2026)

[Compare
Source](https://redirect.github.com/pyparsing/pyparsing/compare/3.3.1...3.3.2)

- Defined pyparsing-specific warning classes so that they can be
selectively enabled
or disabled without affecting warnings raised by other libraries in the
same Python
  app:
- `PyparsingWarning` - base warning for all pyparsing-specific warnings
(inherits
    from `UserWarning`)
- `PyparsingDeprecationWarning` - warning for using deprecated features
(inherits
    from `PyparsingWarning` and `DeprecationWarning`)
- `PyparsingDiagnosticWarning` - warning raised when pyparsing
diagnostics are
enabled and a diagnostic feature is used (inherits from
`PyparsingWarning`)

- Added `as_datetime` parse action to `pyparsing.common` - a more
generalized
version of the `convert_to_datetime` parse action (supports any
expression that extracts
date/time fields into "year", "month", "day", etc. results names), and
validates
  that the parsed fields represent a valid date and time.

- Added `iso8601_date_validated` and `iso8601_datetime_validated`
expressions to
  `pyparsing.common`, which return a Python `datetime.datetime`

- Various performance improvements in `ParseResults` class and core
functions, with
  10-20% performance overall.

- Added `regex_inverter` web page (using PyScript) to demonstrate using
the `inv_regex.py`
  example.

- Expanded regex forms handled by the `examples/inv_regex.py` example:
  - named capturing groups (`?P<name>`)
  - partial repetition (`{m,}` and `{,n}`)
  - negated character classes (`[^...]`)

- Added `SPy` (Simplified Python) parser to examples.

###
[`v3.3.1`](https://redirect.github.com/pyparsing/pyparsing/blob/HEAD/CHANGES#Version-331---December-2025)

[Compare
Source](https://redirect.github.com/pyparsing/pyparsing/compare/3.3.0...3.3.1)

- Added license info to metadata, following PEP-639. Thanks to Gedalia
Pasternak and
Marc Mueller for submitted issue and PR. Fixes
[#&#8203;626](https://redirect.github.com/pyparsing/pyparsing/issues/626).

###
[`v3.3.0`](https://redirect.github.com/pyparsing/pyparsing/blob/HEAD/CHANGES#Version-330---December-2025)

[Compare
Source](https://redirect.github.com/pyparsing/pyparsing/compare/3.2.5...3.3.0)


\===========================================================================================
The version 3.3.0 release will begin emitting `DeprecationWarnings` for
pyparsing methods
that have been renamed to PEP8-compliant names (introduced in pyparsing
3.0.0, in August,
2021, with legacy names retained as aliases). In preparation, I added in
pyparsing
3.2.2 a utility for finding and replacing the legacy method names with
the new names.
This utility is located at `pyparsing/tools/cvt_pep8_names.py`. This
script will scan all
Python files specified on the command line, and if the `-u` option is
selected, will
replace all occurrences of the old method names with the new
PEP8-compliant names,
updating the files in place.

Here is an example that converts all the files in the pyparsing
`/examples` directory:

```
  python -m pyparsing.tools.cvt_pyparsing_pep8_names -u examples/*.py
```

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/googleapis/python-spanner-sqlalchemy).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My40OC4xIiwidXBkYXRlZEluVmVyIjoiNDMuNDguMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->