Structure error references in range [C1801, C2000]

[Rageking8]

This is batch 8 that structures error/warning references. See #5465 for more information.

[prmerger-automator]

@Rageking8 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 41910e1:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/error-messages/compiler-errors-1/fatal-error-c1852.md	✅Succeeded
docs/error-messages/compiler-errors-1/fatal-error-c1853.md	✅Succeeded
docs/error-messages/compiler-errors-1/fatal-error-c1854.md	✅Succeeded
docs/error-messages/compiler-errors-1/fatal-error-c1900.md	✅Succeeded
docs/error-messages/compiler-errors-1/fatal-error-c1902.md	✅Succeeded
docs/error-messages/compiler-errors-1/fatal-error-c1903.md	✅Succeeded
docs/error-messages/compiler-errors-1/fatal-error-c1904.md	✅Succeeded
docs/error-messages/compiler-errors-1/fatal-error-c1905.md	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
File Change Percent	This PR contains file(s) with more than 30% file change.

[v-dirichards]

@TylerMSFT

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[TylerMSFT]

I like having the Remarks header. It's nice to separate the text of the error from the explanation so that it's easier to tell which is which.

[TylerMSFT]

#sign-off