Feature/change account details 29

[Toxsuh]

Issues

Closes #59
I know the branch is opened as 29 not 59 but the ticket is actually 59 my apologies

Description

• Loosened the update access rule on users collection so a logged-in user can update their own row
• Added a server action updateAccount in userDashboard page that re-verifies the current password via payload.login() before applying any change, then calls payload.update() with the requesting user's access context
• Edits to userDashboard page for account detail changing
• Wrapped the form in a client component UserAccountForm, uses useActionState for success/error handling and pending state
• Footer also adjusted, no longer has negative padding and encroaches on site space for smaller pages

Checklist

• Make sure you are requesting to pull a feature/fix branch (right side). Don't request the main branch!
• Make sure you are making a pull request against the main branch (left side). Also you should start your branch off main branch.
• I have added tests that prove my fix is effective or that my feature works.
• I have added the necessary documentation (if appropriate).

How To Review

Users collection to check if access handling is ok
then changes to userDashboard and finally the UserAccountForm component

Notes

• We don't have email verification, nor is our email form actually unique in the users collection. While users can't switch to an already existing email (blocked by code in userDashboard), they can make new accounts with the same email. (I think)
• Error message on duplicate emails is Payload's default validation message, instead of our own message. Currently it says something like "Value must be unique" instead of "This email is already linked to an account".
• Similarly, the error on current-password verification only comes up as "Incorrect password" instead of the actually valid error such as "Too many logins in a short amount of time. Please try later" etc etc.

[ShazeelAli]

Still need to double check functionalty fully but seems good, just make the requested change if able

[ShazeelAli]

Could you try using something like this for the error catch rather than err:any

catch (err) {
if (err instanceof Error) {
return { status: 'error', message: err.message }
}
return { status: 'error', message: 'An unexpected error occurred' }
}

[Toxsuh]

Changed to add bucket error handling :D

[ShazeelAli]

Nice changes