Fix/login error

[giurigaud]

What problem is this solving?

Buyers can't login if there is misconfiguration in organizations/cost centers

(REOPEN PR - change validation to check if cost center exists)

How should this be manually tested?

1- create Org
2- create CC1
3- create CC2
4- associate user 1 with CC1
5- associate user 1 with CC2
6- delete CC1
7- try to log in with user 1

Screenshots or example usage:

Before change
https://github.com/user-attachments/assets/c874c3a0-e458-4881-81d3-e6b52bda7a5e

After change

Uploading deleteCostCenter-afterChange.mov…

Uploading deleteCostCenter-afterChange.mov…

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[github-actions]

	Messages
📖	❤️ Thanks!
📖	🎉 PR additions = 9, PR deletions = 2

Generated by 🚫 dangerJS against 9fb56e8

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 1.45.0 → 1.45.1

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.storefront-permissions@1.45.1

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖