Bump pyright from 1.1.375 to 1.1.376 in /.github (#427)

Bumps
[pyright](https://github.com/Microsoft/pyright/tree/HEAD/packages/pyright)
from 1.1.375 to 1.1.376.
<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.376</h2>
<p>Bug Fixes:</p>
<ul>
<li>Fixed bug that results in a crash when an empty tuple is used to
specialize a generic type alias parameterized by a ParamSpec.</li>
<li>Fixed a bug that results in a false positive
reportInconsistentOverload error when the implementation of the overload
includes a decorator that changes the type of the implementation to a
non-function type.</li>
<li>Fixed bug that results in a false positive error when type argument
for <code>Literal</code> doesn't follow type expression rules within a
value expression context.</li>
<li>Fixed regression that resulted in a hang when determining whether an
overload implementation with generics was compatible with its
overloads.</li>
<li>Fixed bug that results in a false negative
<code>reportIncompatibleMethodOverride</code> when the child class
method uses a type parameter that is scoped to the child class.</li>
<li>Fixed bug that produces signatures with extra (unnecessary)
positional-only and keyword-only separators when using a TypedDict with
zero fields.</li>
<li>Improved consistency of parameter name restrictions for the
<code>reportSelfClsParameterName</code> check. Previously, different
rules were applied to <code>__new__</code> and class methods within
metaclasses.</li>
<li>Fixed a false positive error when solving type variables in a call
that involves a lambda.</li>
<li>Fixed bug that results in a confusing type in an error message when
<code>isinstance</code> type narrowing between a <code>type</code> and
another type creates a subclass.</li>
<li>Fixed bug that leads to false positive error when a protocol has a
read-only property a class has a Final variable.</li>
<li>Fixed bug that leads to a hang under certain circumstances involving
deeply-nested higher-order functions.</li>
<li>Fixed bug that results in a confusing type in an error message when
<code>isinstance</code> type narrowing between a <code>type</code> and
another type creates a subclass.</li>
</ul>
<p>Enhancements:</p>
<ul>
<li>Enhanced argument-to-parameter matching logic to support dictionary
unpacking where the dict key type is a union of literals.</li>
</ul>
<p>Behavior Changes:</p>
<ul>
<li>Changed composition of settings that affect type checking behaviors.
Previously, some LSP settings that affect type checking could override
config files. Now, the config file always &quot;wins&quot;. Command-line
parameters passed to the CLI version of pyright win over both LSP
settings and config files.</li>
<li>Changed synthesized comparison methods (<code>__lt__</code>, etc.)
for dataclasses when <code>order=True</code> to use <code>Self</code>
rather than an instance of the class. This is not only more consistent
with other synthesized methods, but it also preserves covariance of type
variables if the dataclass is frozen.</li>
<li>Changed behavior for protocols that have methods with method-scoped
type variables. These are no longer treated as free type variables
during protocol matching, so they can be used to support rank-2
polymorphism. This behavior is not currently dictated by the typing
spec, but it is more consistent with mypy.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/microsoft/pyright/commit/7fd5ed20beea0a68fa9d7430c65b9c0f2ac265dd"><code>7fd5ed2</code></a>
Published 1.1.376</li>
<li><a
href="https://github.com/microsoft/pyright/commit/07ca233ba7076a36882bcfb4ddfcf16d95e0a39e"><code>07ca233</code></a>
Updated typescript compiler version from 5.2 to 5.5.4 to avoid a bug I
was hi...</li>
<li>See full diff in <a
href="https://github.com/Microsoft/pyright/commits/1.1.376/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.375&new-version=1.1.376)](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>

.github/package.json

@@ -1,5 +1,5 @@
 {
 	"devDependencies": {
-		"pyright": "1.1.375"
+		"pyright": "1.1.376"
 	}
 }