test(integration/gatsby-cli): use sandboxed directory to "globally" install gatsby-cli

[pieh]

Relies on #27055

This installs gatsby-cli in some /tmp directory and let tests use that installation to invoke global gatsby-cli commands.

Those changes are looking to catch problems like #26919 which was not caught by any automatic testing (it worked on CI because executed gatsby-cli was in nested monorepo directory so it had access to all node_modules which did hide some problems)

---

This is part of PR series:

1. feat(gatsby-dev-cli): install deps if there are no gatsby deps but --forceInstall was used
2. test(integration/gatsby-cli): use sandboxed directory to "globally" install gatsby-cli (THIS PR)
3. chore(gatsby-recipes): bundle dependencies
4. chore(gatsby-cli): bundle dependencies

[laurieontech]

Looks good so far. Using a tmp dir is definitely prefered.

[pieh]

I dropped chaining commands with && in favour of this so the script fails when any command fails (with exception to if statement conditions in this case)

check https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html for set command (and -e flag in particular) explanation

[pieh]

Just to showcase that this continue to fail tests properly - https://app.circleci.com/pipelines/github/gatsbyjs/gatsby/50132/workflows/a257b5b7-1e8c-4de1-9854-77c7e530725b is the intentionally not passing jest test ( from temporary draft PR just to test that - #27182 )

[pieh]

(and reason for dropping chaining is that becomes unreadable with conditional commands - like the chmod that is only done if the file actually exists that I added in this PR)

[gatsby-cloud]

Gatsby Cloud Build Report

gatsby

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 4m

[laurieontech]

I'd recommend @wardpeet as a second set of eyes on this. It seems reasonable to me.

[wardpeet]

Looks good to me 👍

[wardpeet]

I've tested on windows and it all work