Prevent creation of .md-e files in the docs

[dhruvkb]

Description

Currently the pre-commit lint step uses sed to ensure that we do not use ```console in the documentation and instead replace it with ```bash.

The sed command works for Linux but is interpreted differently on macOS where -i -e is interpreted as -i='-e' and causes .md-e files to to be created for every documentation file when linting using just lint. Using perl can avoid this problem as that approach is cross-platform (provided perl is installed, which is usually is).

This also updates another script that used a similar construct in a different script (with the working and broken operating systems reversed) with perl.

Testing Instructions

1. Check that lint step in CI passes.
2. Intentionally change some occurrences of ```bash to ```console in the docs.
3. See that pre-commit does not allow you to commit these mistakes.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[sarayourfriend]

LGTM! Worried we might be playing whack-a-mole switching between various tools presumed to be installed and behave the same across platforms, but perl sounds like a good next choice. Hopefully it continues to work 😁