Bug 2026892

First of all, VTE ships its own Bash configuration snippet in /etc/profile. /vte.sh that already does this and provides the definition of the __vte_prompt_command function. So it's better to let VTE own its own configuration.

Secondly, this creates problems in interactive Bash instances running inside a container that doesn't have VTE installed but has the VTE_VERSION environment variable set, because PROMPT_COMMAND tries to access a missing __vte_prompt_command function. This is observed in Toolbox containers created from the Red Hat Universal Base Image. Toolbox containers inherit environment variables like TERM and VTE_VERSION from the host so that interactive shells inside the container are configured like the ones on the host. However, UBI doesn't have /etc/profile.d/vte.sh. Hence, instead of silently ignoring the VTE specific configuration bits, PROMPT_COMMAND ends up trying to access a missing __vte_prompt_command function.

[ This is important because we are going to ship Toolbox in RHEL 9.0. ]