Revert PR #3359 as this is breaking stuff for many folks. Need to rethink how we handle system defaults differently on this
Respect original PATH definitions on install

The exporting of PATH as a fixed string would clobber any system-wide
paths added to env after installation. Instead, we now read any existing
PATH exports from previous config files and copy those from the user's
bash config, or else default to a basic prepend-only example that
respects the system environment.
Use sed instead

This needs the extra newline character defined in a variable because
shells treat the ${} expansion differently for replacing newline characters.