`Microsoft.Extensions.StaticAnalysis` should be mentioned/encouraged in this documentation

### Type of issue

Missing information

### Description

In the later sections of the page, many external analyzers are mentioned, but `Microsoft.Extensions.StaticAnalysis` is completely absent. I assume that this is because that project/package is somewhat new, and the docs here were never updated to mention it.

Instead of initially pushing people towards random third-party packages, the docs should first propose using `Microsoft.Extensions.StaticAnalysis` as a best practice.

### Page URL

https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/overview?tabs=net-10#code-style-analysis

### Content source URL

https://github.com/dotnet/docs/blob/main/docs/fundamentals/code-analysis/overview.md

### Document Version Independent Id

128f9903-971d-6a66-a2cb-9b12acbc55e7

### Platform Id

6c404312-136c-21aa-d92a-1cb8ea7ecdcf

### Article author

@gewarren

### Metadata

* ID: f8906b2c-b984-0427-d064-829e7ea2fc55
* PlatformId: 6c404312-136c-21aa-d92a-1cb8ea7ecdcf
* Service: **dotnet-fundamentals**

[Related Issues](https://github.com/dotnet/docs/issues?q=is%3Aissue+is%3Aopen+128f9903-971d-6a66-a2cb-9b12acbc55e7)

Open docs/fundamentals/code-analysis/overview.md and read the Code style analysis section referenced by the issue. Add Microsoft.Extensions.StaticAnalysis as the recommended best-practice option before the external analyzers, then verify the rendered wording and links are accurate.

Written by the indexing model from the issue text.