Don't newly create .bash_profile

[tats-u]

Fixes #99

I don't know how to test the new behavior in WSL

echo $'#!/bin/sh\necho OK' > ~/.local/bin/env-test && chmod +x ~/.local/bin/env-test
# Modify profile using starbase
PATH="$(getconf PATH)" sh -lc env-test

[milesj]

Thanks! Will merge through the errors since they are unrelated.

[tats-u]

@milesj

https://github.com/moonrepo/proto/blob/9f47f9d60c9d7f74b38bfc96ced8be1e012422fb/crates/cli/src/shell.rs#L32

Check in reverse order as the most common profile is always last in the list

https://github.com/moonrepo/proto/blob/9f47f9d60c9d7f74b38bfc96ced8be1e012422fb/crates/cli/src/shell.rs#L128-L133

Really? I thought the first is the most preferred one...

Is it why .bashrc is inappropriately suggested first here (proto setup)?

[tats-u]

the most common profile is always last in the list

If so, I wonder why .bash_profile here comes first here.

starbase/crates/shell/src/shells/bash.rs

Lines 81 to 85 in 38035a6

	vec![
	home_dir.join(".bash_profile"),
	home_dir.join(".bashrc"),
	home_dir.join(".profile"),
	]