Automatic deprecation date linting on release

[augustasgri]

There was an eslint rule created which, upon execution, adds appropriate deprecation dates to deprecated elements. Those dates inform developers when a specific deprecated element might be removed from code.

The issue that is being solved can be found in this engineering working group discussion

Main goal would be modifying current itwin-core pipelines such, that upon releasing a new itwin-core version the following would happen:

• Before mentioned eslint "deprecation" rule would be run on release branch to add deprecation dates where they don't exist or replace existing, already passed dates with comment implying that code now may be removed.
• The changes on deprecation comments are mirrored on the master branch as well