Remove username from raw_user_meta_data

[jproberson]

PR Checklist

• - Unit and/or e2e tests for the changes that have been added (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Refactoring (no functional changes)
• Documentation
• Other:

What is the new behavior?

Describe the new behaviour
If useful, provide screenshot or capture to highlight main changes

Does this PR introduce a DB Schema Change or Migration?

• Yes
• No

Git Issues

Closes #

What happens next?

Thank you for the contribution! We will review it ASAP.

If you need more immediate feedback you can reach out to us on Discord in the Community Platform development channel.

[cypress]

onearmy-community-platform    Run #8471

Run Properties:   Passed #8471  •  7f5d6145e4: Merge branch 'master' into feat/remove-raw_user_meta_data

Project	onearmy-community-platform
Branch Review	feat/remove-raw_user_meta_data
Run status	Passed #8471
Run duration	06m 51s
Commit	7f5d6145e4: Merge branch 'master' into feat/remove-raw_user_meta_data
Committer	Mário Nunes
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	2
Pending	0
Skipped	0
Passing	90
View all changes introduced in this branch ↗︎

[benfurber]

@jproberson Can I get a description for this please to understand why this change is being proposed?

[mariojsnunes]

@benfurber currently we store the username on the auth.users object, it was essential for the firebase migration.
But it causes 2 issues:

• in case an account exists in multiple tenant, the username must be the same across them
• harder to change the username

It is also one more thing adding complexity now that we are also looking into creating accounts without profiles (in a first step, for the memberships flow)

This PR is to investigate if we can safely get rid of it, or there is some dependency.

[mariojsnunes]

@jproberson there are still some references to user_metadata

ensureProfile() is how we allow seamless login to each tenant if the user has already registered once.
Need an alternative to that, either:

• have a UI to prompt the user for a username
• create the profile without the username - need to see what are the edge cases here
• get the username from another tenant (via supabase admin rpc)

send-email edge function:

• fetch the profile via auth_id, or
• change the email message to not include the username

fetch a research item with updates - it's required due to collaborators being stored as a list of usernames:

• just make an additional query to the current user profile to get the username, or
• migrate the collaborators to use ids instead - might be worth doing eventually

search projects - to search by author:

• just make an additional query to the current user profile to get the username