THP ELF assembly: Add .note.GNU-stack section

[jayaddison]

This indicates to GNU binutils that it can unset the executable stack flag on the binary that it is building.

Refs: #17933

cc @gabrielschulhof @bnoordhuis (from the git shortlog in this part of the codebase)
cc @danbev (as discussed, for review)

Two developer notes to aid review:

• Some other examples on the web instruct to use %progbits with a percentage symbol. The approach here uses @progbits instead, which is the form documented in the binutils documentation here.
• The conditional block does not check for a Linux-based build environment; this is intentional since node is a cross-platform binary and I believe this section could be relevant for other platforms.

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.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/36580/

[jayaddison]

It looks like clang is complaining when building binaries from b4f3e39, and I think the cause may be related to the ordering of the sections within the .S file.

Theory, based on the error message: clang considers that the __node_text_start: reference should be placed within the.note.GNU-stack section (since it is appears below it in the file); but this section is then discarded since it is a note, meaning that the (required) object reference is lost.

For reference since the build logs may disappear, the error message is:

`__node_text_start' referenced in section `.text' of /home/runner/work/node/node/out/Release/obj.target/libnode/src/large_pages/node_large_page.o: defined in discarded section `.note.GNU-stack' of /home/runner/work/node/node/out/Release/obj.target/node_text_start/src/large_pages/node_text_start.o

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/36584/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/36589/

[jayaddison]

@danbev Could you try re-running the NodeJS CI tests, if that's possible? The failure for bd478f3 seems related to a flaky test, so perhaps a re-run might clear it.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/36620/

[danbev]

Landed in 90008f8.