Remove sudo requirement from install & uninstall scripts

[luispadron]

Resolves #2806
Request for comments document (if applies):

Short description 📝

This PR removes the need to require sudo access. This is problematic in contexts where TTY is not available to enter password (such as in CI/CD). This also makes it more clear that the install script isn't doing anything crazy on someones machine that would require sudo.

Checklist ✅

• The code architecture and patterns are consistent with the rest of the codebase.
• The changes have been tested following the documented guidelines.
• The CHANGELOG.md has been updated to reflect the changes. In case of a breaking change, it's been flagged as such.
• In case the PR introduces changes that affect users, the documentation has been updated.

[fortmarek]

Do we know why sudo was there in the first place?

[luispadron]

@fortmarek Im not entirely sure! @pepibumur would you have more context?

[fortmarek]

I'm OK with this being merged but I would very much curious why it was there in the first place cc @pepibumur

[pepicrft]

@fortmarek Im not entirely sure! @pepibumur would you have more context?

@luispadron I remember having issues when running the installation scripts in M1. It'd be great if the scripts could be tested in that environment. If they work I think it's ok to merge this PR.

[RLovelett]

This is a bit of a blocker for some to even use Tuist. For instance, in our environment sudo is not something we have access to on our managed computers. I worked around this by running the steps of the install script manually.

Also, perhaps adopting a $HOME/.local is also a good fallback if /usr/bin/local is not writable by the current user. I'm less sure I think this is a good general solution. It works for me but I'm not sure it works for everyone.

[fortmarek]

This is a bit of a blocker for some to even use Tuist. For instance, in our environment sudo is not something we have access to on our managed computers. I worked around this by running the steps of the install script manually.

This is unfortunate! I agree it'd be much better if we got around using sudo.

Also, perhaps adopting a $HOME/.local is also a good fallback if /usr/bin/local is not writable by the current user. I'm less sure I think this is a good general solution. It works for me but I'm not sure it works for everyone.

yeah, I'm not sure how often /usr/bin/local is not writable by the user? User could also run the whole install command with sudo to get around that, afaict. We could add some error handling checking the access rights for that directory and then showing error with helpful information if it's actually not writable.

Before merging this, we need someone to test this on M1. @luispadron is currently on vacation, but I believe he should return back soon-ish, so we can move forward with this afterwards.

[pepicrft]

Before merging this, we need someone to test this on M1. @luispadron is currently on vacation, but I believe he should return back soon-ish, so we can move forward with this afterwards.

I can test this one on M1 and merge it if everything works as expected.

[pepicrft]

I confirm this works successfully on M1 so I'll go ahead and merge the PR.