add buck2 RE rust example

[nlopezgi]

• Adding Buck2 RE rust example
• Adding example to CI run
• Fixing a couple of typos in other READMEs
• Fix minor issue with go toolchain with latest version of Buck2

[TheGrizzlyDev]

You're using rbe as a target platform instead of an exec platform, which isn't quite accurate, is there a way to tell buck2 it's an exec platform instead?

[TheGrizzlyDev]

You're using rbe as a target platform instead of an exec platform, which isn't quite accurate, is there a way to tell buck2 it's an exec platform instead?

this comment is still pending, you're incorrectly using target platforms. You aren't targetting RBE, you're using it to run actions.

[nlopezgi]

You're using rbe as a target platform instead of an exec platform, which isn't quite accurate, is there a way to tell buck2 it's an exec platform instead?

this comment is still pending, you're incorrectly using target platforms. You aren't targetting RBE, you're using it to run actions.

Apologies I had missed it.
I do not think there is a way to let buck2 select the execution platform from the command line.

• I looked at https://buck2.build/docs/users/commands/targets/ and there does not seem to be a flag that works for this purpose
• I read over https://buck2.build/docs/rule_authors/configurations/ and my understanding is the targets themselves would need to have the exec_compatible attrs as illustrated by the current way this is set for the other buck2 examples, which I am replacing for use of the --target_platform flag in https://github.com/EngFlow/example/pull/372/files.
• A related issue How to use multiple execution platforms facebook/buck2#612 explains that restrictions for exec platforms need to be set on the targets.

Let me know if you prefer to have the exec_compatible attrs on the targets, if the current solution is an acceptable compromise or if you want me to explore other options.

[TheGrizzlyDev]

This whole file is oddly formatted, can you please fix it?

[nlopezgi]

Not sure which bit exactly you find has the odd formatting.

The only clear think I could see is the use of spaces in some of the section entries. I removed some of the spaces in the sections. However, it seems to me there is a mix in other .buckconfig files of the use of space for entries in secions or no spaces. See for example: https://github.com/facebook/buck2/blob/main/examples/with_prelude/.buckconfig and examples in https://buck2.build/docs/concepts/buckconfig/#configuration-files-can-include-other-files that do have the leading spaces in the entries.
Let me know if it was something else that you found odd about the formatting.