lang/rust: Bump revisions after 1.87.0

PR:		286829

textproc/gnugrep (dependencies): do not rely on compatibility symlink

Historically we had built and installed GNU grep programs as `grep' +
[ef]grep, but started to configure the port with `--program-prefix=g'
in 2022, as we and several other non-GNU/Linux systems, e.g. NetBSD,
OpenBSD, Solaris, macOS do for miscellaneous GNU utilities.  To avoid
breaking POLA, g-prefixless compatibility symlinks were being created,
subject to the COMPAT option (on by default).

Recently GNU grep developers decided to deprecate {e,f}grep variants,
with the clear intention to consolidate all three greps into a single
command.  This had significantly annoyed users who could not update
their scripts to `grep -[EF]', usually for portability reasons, e.g.
SunOS 4.11 grep which does not support those switches, but does have
egrep and fgrep, or when scripts are written by others and they don't
have permissions to modify them, etc.  Perhaps it is time to turn the
COMPAT option off by default, this commit concludes the preparation.

PR:		277784
Requested by:	fuz, obrien

lang/rust: Bump revisions after 1.86.0

PR:		285840

devel/xtensa-esp-elf: Use SETENVI and WRK_ENV to fix build with poudriere-devel

PR:		285720
Reported by:	arrowd

lang/rust: Bump revisions after 1.85.0

PR:		284884

devel/xtensa-esp-elf: Update pkg-descr

The current version of the toolchain should work for versions 5.2.X
and 5.3.X of the esp-idf.

lang/rust: Bump revisions after 1.84.0

PR:		283962

lang/rust: Bump revisions after 1.83.0

PR:		283000

lang/rust: Bump revisions after 1.82.0

PR:		282516

Mk/Uses/cargo.mk: Remove cross-compilation options for Rust-based ports

Reasons:
* Port build shouldn't use cross-compilation mode
  because it buids for the same architecture.
* RUSTFLAGS isn't passed to the build of all or some Rust ports
  in the cross-compilation mode.

Essential changes:
* Remove the CARGO_BUILD_TARGET make variable.
* Remove CARGO_BUILD_TARGET and CARGO_TARGET_* from CARGO_ENV.
* Update many ports that used CARGO_BUILD_TARGET.
* Build paths now don't include the architecture triplet part.

Immadiate benefits:

devel/xtensa-esp-elf: Fix toolchain version string

xtensa-esp32-elf-cc was reporting:

    xtensa-esp-elf-cc (crosstool-NG UNKNOWN) 13.2.0

Update to correctly show the version of crosstool used:

    xtensa-esp-elf-cc (crosstool-NG esp-13.2.0_20240530) 13.2.0

devel/xtensa-esp-elf: Fix i386 build, mark armv7 BROKEN

portsfallout.com flagged the armv7 issue.

devel/xtensa-esp-elf: Add espressif bin wrappers

Build and install the espressif rust based wrapper.

According to upstream, the target xtensa cpu is set via the
XTENSA_GNU_CONFIG environment variable for gcc 12 and later.

In addition to esp32 the esp32s2 and esp32s3 target cpus are now
supported.

While we're here, change to USE_GCC=yes:build.

PR:		281951

devel/xtensa-esp32-elf: Update to 13.2.0_20240530, rename to xtensa-esp-elf

This updates the toolchain to gcc 13.2.0 as used by versions 5.2.2,
5.3.0, and 5.3.1 of the Espressif esp-idf.

The crosstool.config for xtensa-esp32-esp is invalid for this version
(and is removed in esp-14.2.0_20240906 via 6269489 -- "samples:
remove obsolete xtensa-esp32XX-elf targets") so switch to xtensa-esp-esp
and rename port to match.

This update removes the final dependency on gcc10.

PR:		278061 278062