Fixed check for outside assets on user update validation

[snipe]

This clarifies the validation on user editing to only throw a failure if the user has asset that belong to a different company ID. (It was previously incorrectly throwing a validation error if the user had any assets assigned, regardless of the company the assets belong to.)

[what-the-diff]

PR Summary

• Improved Validation Logic
  The rules regarding user switching between companies have been tightened. Now, we will check if a user has any assets tied to a different company before allowing a change of company. This ensures that users can't mistakenly leave a company with important items still associated with their previous company.

• Better Erroneous Switch Message
  We've made our error messages more informative. When a user attempts to switch a company but he/she has items assigned from another company, our new error message clearly tells that. Now, it's easier to understand why a request might have failed.

• Interactive Company Names
  The user's company name will now display as a clickable link (provided the user has the necessary permissions). This makes it quicker and easier for the user to navigate to their company page.

• Clearer Test Names
  We've given our tests more descriptive names. The tests that check whether users can change companies if they have items assigned from another company now have names that reflect their purpose. This improvement will make our testing process more intuitive and transparent.

• Additional Test Scenarios
  We have added new tests to confirm the proper functioning of user updates when assets are assigned to the same company. This ensures that the process of changing a user’s associated company remains smooth even when assets are involved. It also guarantees a comprehensive checks-and-balances system keeping the asset ownership and company switch in harmony.

[uberbrady]

Very nice tests! I like that; a lot!

This reads pretty cleanly to me, great work!