Add eslint plugin yml to enable correct YAML parsing

[lyqht]

Description

While working on #2854, I realized that linting & formatting is not applied to the .yml files. Hence this PR adds them.

Example of invalid YAML file giving 1 error

Notes

There are a few available yml configurations as per the plugin, but I applied the yml:base configuration for now as currently there are a few files that would fail the recommended/standard configuration (the 70+ errors above). It's up to the maintainers if they prefer those instead.

P.S. I didn't create an issue, but I hope this get a hacktoberfest-accepted label 😆

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run lint:js -- --fix and/or npm run lint:md -- --fix for my JavaScript and/or Markdown changes.
  • This is important as most of the cases your code changes might not be correctly linted
• I have run npm run test to check if all tests are passing, and/or npm run test -- -u to update snapshots if I created and/or updated React Components.
• I have checked that the build works locally and that npm run build work fine.
• I've covered new added functionality with unit tests if necessary.

[codecov-commenter]

Codecov Report

Base: 66.02% // Head: 63.82% // Decreases project coverage by -2.20% ⚠️

Coverage data is based on head (adbb194) compared to base (fd57b87).
Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2868      +/-   ##
==========================================
- Coverage   66.02%   63.82%   -2.21%     
==========================================
  Files         118      124       +6     
  Lines        1351     1465     +114     
  Branches      342      367      +25     
==========================================
+ Hits          892      935      +43     
- Misses        422      490      +68     
- Partials       37       40       +3     

Impacted Files	Coverage Δ
src/__fixtures__/hooks.tsx	100.00% <ø> (ø)
src/__fixtures__/page.tsx	94.11% <ø> (-5.89%)	⬇️
...components/ApiComponents/Components/ApiHeading.tsx	0.00% <ø> (ø)
...rc/components/ApiComponents/Components/ApiLink.tsx	0.00% <ø> (ø)
...ents/ApiComponents/Components/SourceLink/index.tsx	0.00% <ø> (ø)
...ApiComponents/Components/VersionSelector/index.tsx	0.00% <ø> (ø)
src/components/ApiComponents/index.tsx	0.00% <ø> (ø)
src/components/Article/index.tsx	100.00% <ø> (ø)
src/components/Banner/index.tsx	100.00% <ø> (ø)
src/components/Codebox/index.tsx	100.00% <ø> (ø)
... and 80 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[ovflowd]

The plugin and changes make sense to me.

Plug-ins have been cleaned out. Only a minor suggestion remains

[nschonni]

@lyqht I pushed a few commits to tie the check back to the CI. It's flagging one file if you want to run the format again locally to address the last file

[lyqht]

@nschonni haha i hope that's the 1 file you're talking about 😆

[ovflowd]

@nschonni don't forget please to add the hacktoberfest-accepted PRs for hacktoberfest PRs 🙈

[nschonni]

You don't actually need the label if the repo has the tag and the PR is merged https://hacktoberfest.com/participation/#pr-mr-details. The label doesn't hurt though, and I have slapped it on a few, since it might speed up the PRs being counted as accepted. Otherwise, merged PRs get counted after 7 days

[ovflowd]

Oooh, that I didn’t know 👀 thanks for explaining!

[nschonni]

The tag is also helpful if you want it to count, but might not be able to land it before the event ends

[ovflowd]

Thank you, Nick! That’s very informative 🙏