Move from doc-warden to an off-the-shelf markdown linter

[scbedd]

• azure-sdk-for-java
• azure-sdk-for-python
• azure-sdk-for-js
• azure-sdk-for-net

There is changelog verification as part of the release process now.

[weshaggard]

We might consider retiring doc-warden all together and implementing some more common MD linting tools which I've been told (but not verified) can help with general readme formatting and structure.

[chidozieononiwu]

We can use Markdown Linter to replace DocWarden.
It has this rule which can be used to enforce the required headers, there is also the ability to specify files to be omitted
I think those are the main things being provided by Docwarden. @scbedd Is that right?

[scbedd]

doc-warden currently supports any pattern of headers. Check the .net .docsettings .

Notice the

and under header Y, we also have sections X, Z

[heaths]

Markdown Linter that @chidozieononiwu referenced is part of the Microsoft Docs Extension Pack for VS code, which Microsoft Docs (now Learn) recommends you install. Many of those components are also used in the pipeline that Docs uses, so could we talk to them and maybe align on that such that all our docs across Microsoft properties (e.g. .NET, various SDKs, general Docs, samples, etc.) are using the same set of rules?

[kurtzeborn]

The title of this issue is misleading. The likely best outcome from this issue that we transition away from doc-warden to an off-the-shelf MD linter.