Structure error references in range [LNK2001, LNK2039]

[Rageking8]

LNK2022 is skipped to prevent potential merge conflicts with #5727. A separate PR will be issued once that is merged.

This is batch 116 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 4c42cd4:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/error-messages/tool-errors/linker-tools-error-lnk2001.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2004.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2005.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2008.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2011.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2013.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2017.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2019.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2020.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2023.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2026.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2027.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2028.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2031.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2033.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2038.md	✅Succeeded
docs/error-messages/tool-errors/linker-tools-error-lnk2039.md	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Changed Files	This PR contains more than 10 changed files.
File Change Percent	This PR contains file(s) with more than 30% file change.

[v-regandowner]

@TylerMSFT - Can you review the proposed changes? Editorial changes LGTM.

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