Update javascript.md

[ntwb]

Follow up to #66 to update markdown format for https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/#type-checks

This resolves most issues with this file except for these four issues:

wordpress-coding-standards/javascript.md:44:59 MD033/no-inline-html Inline HTML [Element: sup]
wordpress-coding-standards/javascript.md:45:96 MD033/no-inline-html Inline HTML [Element: sup]
wordpress-coding-standards/javascript.md:46:123 MD033/no-inline-html Inline HTML [Element: sup]
wordpress-coding-standards/javascript.md:48:1 MD033/no-inline-html Inline HTML [Element: a]

For this section of code:

wpcs-docs/wordpress-coding-standards/javascript.md

Lines 44 to 48 in 776433c

	- Any `!` negation operator should have a following space.<sup>*</sup>
	- All function bodies are indented by one tab, even if the entire file is wrapped in a closure.<sup>*</sup>
	- Spaces may align code within documentation blocks or within a line, but only tabs should be used at the start of a line.<sup>*</sup>
	<a name="spacing-whitespace">*</a>: The WordPress JavaScript standards prefer slightly broader whitespace rules than the jQuery style guide. These deviations are for consistency between the PHP and JavaScript files in the WordPress codebase.

This can be updated in a follow up pull request using the footnotes format:

https://www.markdownguide.org/extended-syntax/#footnotes

Possibly the above might not play well in the parser, so performing that as a separate PR will help if it needs to be reverted if it doesn't work, if that's the case using ^1 or ¹ can work in this case

[ntwb]

This removes an ID element conflict with Object further in the file:

https://github.com/WordPress/wpcs-docs/blob/f4af221f54de1d977d154243d64ab46d3f4bc4e2/wordpress-coding-standards/javascript.md#objects