[Feature]: The step Hook vfox to your Shell should mention that a new terminal needs to be opened for the script to work

[linghengqian]

1. Your usage scenarios?

• I was just testing the difference between vfox and sdkman!.

2. What is your expected outcome?

• The step for Hook vfox to your Shell should mention the need to open a new terminal for the script to work. I'm referring to https://vfox.dev/guides/quick-start.html#_2-hook-vfox-to-your-shell .
• 
• At least for Windows 11, after executing if (-not (Test-Path -Path $PROFILE)) { New-Item -Type File -Path $PROFILE -Force }; Add-Content -Path $PROFILE -Value 'Invoke-Expression "$(vfox activate pwsh)"' in PowerShell 7, vfox is not available in the current PowerShell terminal. I need to open a new PowerShell 7 terminal to make it work.
• It might be better to add a hint like Afterward, open a new terminal. to the documentation. Just like https://sdkman.io/install .

[bytemain]

good point, PR is welcome

[linghengqian]

good point, PR is welcome

• I have opened docs: add post-processing for Hook vfox to your Shell #436.