Actually use user's ~/.psqlrc file

[rafbm]

Hey! Happy Bridge customer here. 👋😄

Since as long as I remember, my ~/.psqlrc customizations have never been available in cb psql sessions. Despite this commit, for instance, I think this probably never worked? Related changes in Crystal behavior seem to go a while back.

Here’s the fix, confirmed to work on my machine. (It’s awesome being able to test by just swapping cb for src/cli.cr!)

Given specs were green and still are, I assume that part just isn’t tested so didn’t study the test suite to find where to add it.

[abrightwell]

Hey @rafbm, thanks for the PR. I'll work on including it into the next release.

While I'm sure it is less common, it seems that we might want to also consider what might happen if the user were to make use of the PSQLRC environment variable. More specifically, if the location is outside of the user's home directory. I'll poke at it and let you know if I think we should include here.

I'm not terribly concerned with handling the version specific convention/naming at this time. But perhaps that's something to think about as well, just in case. I'll give that one more thought for later.

Also, this made me curious as to handling the -X, --no-psqlrc option if it were provided given: cb psql <ID> -- -X. Some initial testing seems to suggest that it's not a concern. And it's further supported given that psql will ignore loading/processing .psqlrc when this option is given which is confirmed here and here.

[rafbm]

Great points! Feel free to amend this PR in any way. This was my first interaction with Crystal so you’ll sure be faster than me at any further improvements. 😄