Docs: Adds deprecated callouts to working-with-rules-deprecated page.

[manovotny]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[x] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Added a couple of callouts (title and note) to the working-with-rules-deprecated page to better indicate to readers that the information on the page is deprecated.

I wound up on the working-with-rules-deprecated page via a google search or something, but I didn't notice that the page name had deprecated in it. As I was reading, I was like, this doesn't seem right... Took me a good 15 minutes to realize I was reading the old version. I figured adding a note to the top, similar to the note at the top of the working-with-rules page might be helpful in case anyone else winds up here like I did.

Is there anything you'd like reviewers to focus on?

Not particularly. 😊

[eslint-github-bot]

Hi @manovotny!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag must be one of the following:

  The Tag is one of the following:

  • Fix - for a bug fix.
  • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
  • New - implements a new feature.
  • Breaking - for a backwards-incompatible enhancement or feature.
  • Docs - changes to documentation only.
  • Build - changes to build process only.
  • Upgrade - for a dependency upgrade.
  • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

  You can use the labels of the issue you are working on to determine the best tag.

• There should be a space following the initial tag and colon, for example 'New: Message'.

Read more about contributing to ESLint here

[mdjermanovic]

Thanks for the PR! This change makes a lot of sense.

[mdjermanovic]

LGTM, thanks!

[mdjermanovic]

Thanks for contributing!

[manovotny]

You're welcome! 😊