Bypass cache when getting the profile on the "set alias" flow

We have a cache mechanism in place, which stores the profiles that are fetched. Once deployed with a new alias, the cache is not updated, so it could happen that the user goes to the explorer and makes a change, which causes the next profile deploy to override the other changes. This is an edge case but avoiding the cache mecanism for the aliases would solve the issue.