common-utils bash_prompt overrides ~/.bash_aliases

Description of the issue:

The common-utils container feature is useful, but has some the annoying behavior of unconditionally write to the end of my ~/.bashrc. I'd personally like an option to prevent this behavior, in particular I use my own custom ~/.bash_aliases from my personnel dotfiles repository, in which I define my own PS1 (in general, I keep the default provided ~/.bashrc and just put my own preferences in ~/.bash_aliases) .
Since ~/.bash_aliases would normally be sourced at the very end of a well written ~/.bashrc (as is done in the default provided one) then ~/.bash_aliases should have precedence over any sourced files. But if I use the common-utils container feature, then I am forced to invoke some container lifetime script to bring back my .bashrc to what I want.

Personally, I really don't like verbose prompt string, nor command injection in prompts (they tend to be very slow). I don't have any use for fancy prompts and I'd prefer if the common-utils container feature would have an option to completely disable the bash_prompt feature and not write in any of my dotfiles. (I think appending to user dotfiles is not a good design choice in the first place).

Localiza la configuración de bash_prompt de la feature de contenedor common-utils e inspecciona cómo añade contenido a ~/.bashrc y cómo interactúa con ~/.bash_aliases. Añade una opción para deshabilitar ese comportamiento sin modificar los dotfiles del usuario y, después, verifica que la opción conserva la configuración existente del prompt cuando está habilitada.

Escrito por el modelo de indexación a partir del texto del issue.