R terminal doesn't execute `~/.Rprofile` if renv is enabled and `RENV_CONFIG_USER_PROFILE=TRUE` is set in `~/.Renviron`

Describe the bug
R doesn't execute ~/.Rprofile if renv is enabled and RENV_CONFIG_USER_PROFILE=TRUE is set in ~/.Renviron.

Background: renv is not supposed to source ~/.Rprofile by default, but this can be changed via RENV_CONFIG_USER_PROFILE environment variable.

To Reproduce
Steps to reproduce the behavior:

1. Create an empty project with renv::init()
2. Set RENV_CONFIG_USER_PROFILE=TRUE in ~/.Renviron.
3. Add some diagnostics code to ~/.Rprofile. E.g., cat("hello\n").
4. Open code session in the project directory.
5. Open an R terminal for that project.

Can you fix this issue by yourself? (We appreciate the help)

No

Expected behavior
hello when a new R terminal is started

However, if you start R from terminal in the same directory you see hello.

• OS: macOS and linux
• VSCode Version: 1.82.1
• R Version: 4.3.0
• vscode-R version: 2.8.1

Reproduce the issue with ~/.Renviron setting RENV_CONFIG_USER_PROFILE=TRUE, ~/.Rprofile printing hello, an renv::init() project, and an R terminal. Start by tracing the R terminal startup entry point in the TypeScript extension and compare it with launching R directly; done means the terminal prints hello for the project without breaking normal startup.