Really fix import path for .mjs files

[dhruvkb]

Fixes

Follow up to #3390.

Description

This PR fixes the import path to the .mjs files by using the full path instead of relative as per a comment on this thread: actions/github-script#168 (comment) This should really fix the workflows this time.

A point of confusion is that the docs say that "type": "module" should be present in package.json but import() has been working just fine without that so far (see testing instructions in original PR #3375) so it might just work even without that field.

This PR also removes a redundant step from CI that should considerably speed up the workflow.

Testing Instructions

Compare the code changes against the attached thread.

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.

[obulat]

Why do we remove the setup-env? Is the environment set up in a different way in automations?

[dhruvkb]

When we use actions/github-script, we don't need the environment to be set up.