build(deps-dev): bump pyright from 1.1.353 to 1.1.355 (#452)

Bumps
[pyright](https://github.com/Microsoft/pyright/tree/HEAD/packages/pyright)
from 1.1.353 to 1.1.355.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/Microsoft/pyright/releases">pyright's
releases</a>.</em></p>
<blockquote>
<h2>Published 1.1.355</h2>
<p>Bug Fixes:</p>
<ul>
<li>Fixed a bug that results in incorrect type evaluation if a list
expression includes a generator expression.</li>
<li>Fixed bug that results in a false negative when a TypeAliasType
object is used in a class pattern.</li>
<li>Fixed bug that results in false positive when implicitly
specializing a class parameterized by a TypeVarTuple when there is no
default.</li>
<li>Fixed bug that results in false positive when a list or set
expression is evaluated using bidirectional type inference when the
expected type is <code>MutableSet</code> or
<code>MutableSequence</code>.</li>
<li>Fixed bug that results in a false negative when overriding a method
that has keyword parameters with a method that has a <code>*args</code>
parameter.</li>
<li>Fixed a bug that results in a false positive error in certain
circumstances involving a TypeVarTuple used within an overload.</li>
<li>Fixed bug that results in a false positive error when a base class
defines a writable property and a subclass writes to the property.</li>
<li>Fixed bug that results in a false positive &quot;overload
implementation does not match overloads&quot; diagnostic when
positional-only and keyword-only parameters are involved.</li>
<li>Fixed a bug that results in a false positive in a complex situation
that involves generic protocols, properties, and mix-in classes.</li>
<li>Fixed bug that results in false positive error when a
<code>__new__</code> method in a metaclass uses PEP 692 (unpacked
TypeDict) to annotate its <code>**kwargs</code> parameter.</li>
</ul>
<p>Enhancements:</p>
<ul>
<li>Updated typeshed stubs to the latest. This version of typeshed
replaces the older-style positional-only parameters with PEP 570
syntax.</li>
<li>Improved validation for <code>except</code> and <code>except*</code>
statements to catch some previously-undetected invalid cases.</li>
<li>Expanded handling of python versions to handle more than just
major/minor version numbers. Pyright now handles micro, releaseLevel,
and serial numbers as well.</li>
</ul>
<h2>Published 1.1.354</h2>
<p>Bug Fixes:</p>
<ul>
<li>Fixed a bug that resulted in an incorrect type evaluation when an
augmented assignment is used within an inner-scoped function to add a
constant to a variable. Literal math should not be used in this
case.</li>
<li>Fixed two bugs that resulted in false negatives when redefining a
constant variable with a non-variable symbol and when redefining a Final
variable with a non-variable symbol.</li>
<li>Fixed bug that results in false positive when a generic class or
type alias uses a TypeVarTuple followed by one or more ParamSpecs that
have default values.</li>
<li>Fixed bug that resulted in false negative when narrowing a
constrained or bound TypeVar with a <code>complex()</code> or
<code>float()</code> class pattern.</li>
<li>Fixed bug that results in a false positive under certain
circumstances when a constrained TypeVar is used as the default for
another constrained TypeVar.</li>
<li>Fixed a bug that results in a false positive under certain
circumstances when defining a type alias using the old
<code>typing.TypeAlias</code> annotation.</li>
<li>Fixed a bug that results in a false negative when a class explicitly
inherits from a protocol that defines an instance variable but the child
re-declares as a <code>ClassVar</code> without an explicit type.</li>
<li>Fixed a bug that made locale overrides through environment variables
no longer work on node 21.</li>
</ul>
<p>Enhancements:</p>
<ul>
<li>Enhanced handling of <code>type</code> function when it is passed a
class. Pyright previously evaluated this as <code>Any</code>, but now it
returns the class' metaclass.</li>
<li>Added check for generic classes and type aliases that include a
TypeVarTuple followed by a TypeVar that has a default value. This is
illegal according to PEP 696.</li>
<li>Changed the behavior when accessing a class attribute from a generic
class that is not specialized. The class is now automatically
specialized in the case using default type parameter values (from PEP
696) or Unknown. This change is required for conformance with PEP
696.</li>
<li>(From pylance) Added some optimizations to the tokenizer to reduce
memory usage.</li>
<li>Added new <code>reportUnhashable</code> diagnostic rule.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/microsoft/pyright/commit/a2831b7338ada2534ec91a01a98bc07dfc3509c2"><code>a2831b7</code></a>
Published 1.1.355</li>
<li><a
href="https://github.com/microsoft/pyright/commit/0a73f4b0f5876ba59720b747f6edb9178dcc23c0"><code>0a73f4b</code></a>
Published 1.1.354</li>
<li>See full diff in <a
href="https://github.com/Microsoft/pyright/commits/1.1.355/packages/pyright">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pyright&package-manager=npm_and_yarn&previous-version=1.1.353&new-version=1.1.355)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

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

package.json

@@ -1,5 +1,5 @@
 {
     "devDependencies": {
-        "pyright": "1.1.353"
+        "pyright": "1.1.355"
     }
 }