fix(backend): Fix minor misalignment's with the User FAPI and BAPI classes

[panteliselef]

Description

User FAPI and User BAPI cannot be fully aligned, but we should aim for keeping their signature as similar as possible.

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Packages affected

• @clerk/backend
• @clerk/chrome-extension
• @clerk/clerk-js
• @clerk/clerk-expo
• @clerk/fastify
• gatsby-plugin-clerk
• @clerk/localizations
• @clerk/nextjs
• @clerk/clerk-react
• @clerk/remix
• @clerk/clerk-sdk-node
• @clerk/shared
• @clerk/themes
• @clerk/types
• build/tooling/chore

[changeset-bot]

🦋 Changeset detected

Latest commit: ec8179b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
@clerk/backend	Minor
@clerk/fastify	Patch
gatsby-plugin-clerk	Patch
@clerk/nextjs	Patch
@clerk/remix	Patch
@clerk/clerk-sdk-node	Patch
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[dimkl]

I would suggest we use getters for primaryEmailAddress / primaryPhoneNumber , .... instead of adding them as params. I would also suggest a getter for fullName.
Why did we export the getFullName function? I don't see any import or usage outside the User.ts.

[dimkl]

@panteliselef let's create a ticket to introduce a common interface in @clerk/types and make the BAPI / FAPI User extend it.