docs: layout tweak of caching info, remove toolchain :( and additional info about bazel-remote-cache

[mike-geeves-oxb]

Minor doc improvements

[WorkerPants]

Welcome to the Pantsbuild Community. This looks like your first PR here.

We are so grateful for each an every contribution, big or small.
So thanks for spending your time and energy making this project better.

If you haven't gotten a reply in a week, feel free to gently comment "bump" to ping the project admins.

If you haven't already, feel free to come say hi on Slack.

If you have questions, or just want to surface this PR, check out the #development channel.
(If you want to check it out without logging in, check out our Linen mirror)

Thanks again for this PR, and we'll be on the lookout for your next one 😄!

[benjyw]

Just punctuation nits. Thanks!

[benjyw]

Thanks for this fix! I will cherry-pick it to relevant docs versions.

[WorkerPants]

I tried to automatically cherry-pick this change back to each relevant milestone, so that it is available in those older releases of Pants.

❌ 2.15.x

I was unable to cherry-pick this PR to 2.15.x, likely due to merge-conflicts.

Steps to Cherry-Pick locally

To resolve:

1. (Ensure your git working directory is clean)
2. Run the following script to reproduce the merge-conflicts:

   git checkout https://github.com/pantsbuild/pants main \
     && git pull \
     && git fetch https://github.com/pantsbuild/pants 2.15.x \
     && git checkout -b cherry-pick-19299-to-2.15.x FETCH_HEAD \
     && git cherry-pick 21f377deeaae9fdc30ebb60ccc1851b37844d308

3. Fix the merge conflicts and commit the changes
4. Run build-support/cherry_pick/make_pr.sh -- "19299" "2.15.x"

Please note that I cannot re-run CI if a job fails. Please work with your PR approver(s) to re-run CI if necessary.

❌ 2.16.x

I was unable to cherry-pick this PR to 2.16.x, likely due to merge-conflicts.

Steps to Cherry-Pick locally

To resolve:

1. (Ensure your git working directory is clean)
2. Run the following script to reproduce the merge-conflicts:

   git checkout https://github.com/pantsbuild/pants main \
     && git pull \
     && git fetch https://github.com/pantsbuild/pants 2.16.x \
     && git checkout -b cherry-pick-19299-to-2.16.x FETCH_HEAD \
     && git cherry-pick 21f377deeaae9fdc30ebb60ccc1851b37844d308

3. Fix the merge conflicts and commit the changes
4. Run build-support/cherry_pick/make_pr.sh -- "19299" "2.16.x"

Please note that I cannot re-run CI if a job fails. Please work with your PR approver(s) to re-run CI if necessary.

❌ 2.17.x

I was unable to cherry-pick this PR to 2.17.x, likely due to merge-conflicts.

Steps to Cherry-Pick locally

To resolve:

1. (Ensure your git working directory is clean)
2. Run the following script to reproduce the merge-conflicts:

   git checkout https://github.com/pantsbuild/pants main \
     && git pull \
     && git fetch https://github.com/pantsbuild/pants 2.17.x \
     && git checkout -b cherry-pick-19299-to-2.17.x FETCH_HEAD \
     && git cherry-pick 21f377deeaae9fdc30ebb60ccc1851b37844d308

3. Fix the merge conflicts and commit the changes
4. Run build-support/cherry_pick/make_pr.sh -- "19299" "2.17.x"

Please note that I cannot re-run CI if a job fails. Please work with your PR approver(s) to re-run CI if necessary.

---

When you're done manually cherry-picking, please remove the needs-cherrypick label on this PR.

Thanks again for your contributions!

🤖 Beep Boop here's my run link

[thejcannon]

There wasn't actually a merge-conflict, the GHA code should've been ported by to the older branches.

See: #19322

If you want, once these are fixed (after https://pantsbuild.slack.com/archives/C0D7TNJHL/p1686790197387729 is fixed) we can kick the bot to run on this PR.

[WorkerPants]

I tried to automatically cherry-pick this change back to each relevant milestone, so that it is available in those older releases of Pants.

❌ 2.15.x

I was unable to cherry-pick this PR to 2.15.x, likely due to merge-conflicts.

Steps to Cherry-Pick locally

To resolve:

1. (Ensure your git working directory is clean)
2. Run the following script to reproduce the merge-conflicts:

   git checkout https://github.com/pantsbuild/pants main \
     && git pull \
     && git fetch https://github.com/pantsbuild/pants 2.15.x \
     && git checkout -b cherry-pick-19299-to-2.15.x FETCH_HEAD \
     && git cherry-pick 21f377deeaae9fdc30ebb60ccc1851b37844d308

3. Fix the merge conflicts and commit the changes
4. Run build-support/cherry_pick/make_pr.sh -- "19299" "2.15.x"

Please note that I cannot re-run CI if a job fails. Please work with your PR approver(s) to re-run CI if necessary.

❌ 2.16.x

I was unable to cherry-pick this PR to 2.16.x, likely due to merge-conflicts.

Steps to Cherry-Pick locally

To resolve:

1. (Ensure your git working directory is clean)
2. Run the following script to reproduce the merge-conflicts:

   git checkout https://github.com/pantsbuild/pants main \
     && git pull \
     && git fetch https://github.com/pantsbuild/pants 2.16.x \
     && git checkout -b cherry-pick-19299-to-2.16.x FETCH_HEAD \
     && git cherry-pick 21f377deeaae9fdc30ebb60ccc1851b37844d308

3. Fix the merge conflicts and commit the changes
4. Run build-support/cherry_pick/make_pr.sh -- "19299" "2.16.x"

Please note that I cannot re-run CI if a job fails. Please work with your PR approver(s) to re-run CI if necessary.

❌ 2.17.x

I was unable to cherry-pick this PR to 2.17.x, likely due to merge-conflicts.

Steps to Cherry-Pick locally

To resolve:

1. (Ensure your git working directory is clean)
2. Run the following script to reproduce the merge-conflicts:

   git checkout https://github.com/pantsbuild/pants main \
     && git pull \
     && git fetch https://github.com/pantsbuild/pants 2.17.x \
     && git checkout -b cherry-pick-19299-to-2.17.x FETCH_HEAD \
     && git cherry-pick 21f377deeaae9fdc30ebb60ccc1851b37844d308

3. Fix the merge conflicts and commit the changes
4. Run build-support/cherry_pick/make_pr.sh -- "19299" "2.17.x"

Please note that I cannot re-run CI if a job fails. Please work with your PR approver(s) to re-run CI if necessary.

---

When you're done manually cherry-picking, please remove the needs-cherrypick label on this PR.

Thanks again for your contributions!

🤖 Beep Boop here's my run link

[thejcannon]

Ok that failure was on me. One more before I turn on the seatbelt buckle sign.

Hold on...

[WorkerPants]

I tried to automatically cherry-pick this change back to each relevant milestone, so that it is available in those older releases of Pants.

✔️ 2.15.x

Successfully opened #19330.

✔️ 2.16.x

Successfully opened #19331.

✔️ 2.17.x

Successfully opened #19329.

---

Thanks again for your contributions!

🤖 Beep Boop here's my run link

[thejcannon]

TADA 🎉

[mike-geeves-oxb]

Thanks!
Phew, much effort for a tiny commit 😅 I'll try and do a little bigger next time!

[thejcannon]

Haha, you just happened to be merging at the time where we're investing more in automation. And GHA isn't the easiest thing to get right 😅

[mike-geeves-oxb]

Well, it's a nicer process than the "suggest edits" before so worth it imo 👍 (having tried both at the same time for this one!)

As long as you're not quite at https://xkcd.com/1319

[thejcannon]

Only time will tell, honestly. I chalk up time spent to "learning". I found some interesting and novel ways of testing our GitHub Actions. I also started getting comfortable with https://github.com/actions/github-script and the GitHub Rest API