Bump analyzer from 2.8.0 to 5.1.0

[dependabot]

Bumps analyzer from 2.8.0 to 5.1.0.

Changelog

Sourced from analyzer's changelog.

2.19.0

Language

• Breaking change #49635[]: Flag additional code as unreachable due to types Null and Never. Several unusual constructs that lead to unreachable code are now recognized by flow analysis:

  • Control flow after an expression of the form e ?? other or e ??= other, where e has static type Null and other has static type Never, is considered unreachable.

  • Control flow predicated on an expression of the form e is Never evaluating to true is considered unreachable.

  • Control flow predicated on an expression of the form e is! Never evaluating to false is considered unreachable.

  • Control flow on the RHS of a null-aware access such as e?.property..., e?.property = ... or e?.method(...), where e has static type Null, is considered unreachable (Note: this can arise in the presence of extension methods).

  Previously, these behaviors only took effect if e was a reference to a local variable.

  Additionally, a type test of the form v is Never (where v is a local variable) no longer promotes v to type Never.

• Breaking change #49878[]: Calling ResourceHandle.toFile(), ResourceHandle.toSocket(), ResourceHandle.toRawSocket() or ResourceHandle.toRawDatagramSocket(), more than once now throws a StateError.

  The previous behavior would allow multiple Dart objects to refer to the same file descriptor, which would produce errors when one object was closed or garbage collected.

#49635: dart-lang/sdk#49635 #49878: dart-lang/sdk#49878

• Breaking Change #49687[]: Don't delegate inaccessible private names to noSuchMethod. If a concrete class implements an interface containing a member with a name that's private to different library, and does not inherit an implementation of that interface member, a invocation of that member will result in an exception getting thrown. Previously, such attempts would result in the call being diverted to the noSuchMethod method.

  This change closes a loophole in Dart's privacy system, where another library can provide a different implementation of a supposedly private member using

... (truncated)

Commits

• See full diff in compare view

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 commands and options

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 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)

[dependabot]

Looks like analyzer is updatable in another way, so this is no longer needed.