Add a contributor profile edit option

Community & Support: [LinkedIn Group](https://www.linkedin.com/groups/14656108/) · [Slack #project-nest](https://owasp.slack.com/archives/project-nest)

Active project leaders: Arkadii Yakovets -- [GitHub](https://github.com/arkid15r/) · [LinkedIn](https://www.linkedin.com/in/arkid15r/) · [Slack](https://owasp.slack.com/team/U060W3NKLTF); Kate Golovanova -- [GitHub](https://github.com/kasya/) · [LinkedIn](https://www.linkedin.com/in/kate-golovanova/) · [Slack](https://owasp.slack.com/team/U07PWB1JZ6Z)

[Contributing](https://github.com/owasp/nest/blob/main/CONTRIBUTING.md) · [Code of Conduct](https://github.com/owasp/nest/blob/main/CODE_OF_CONDUCT.md) · [GSoC Mentors](https://github.com/owasp/nest/blob/main/MENTORS.md)

---

**Is your feature request related to a problem? Please describe.**
An editing option provided to each contributor where they can edit their profile information like choose to show their github contribution or not and all the general options like profile image, username, location etc.

**Describe the solution you'd like**
A high level description for how this will be implemented :
- update the data model with new fields to github_users like profile_name_updated
- update the graphql api and mutation (override / update to new values if set, otherwise fall back to GitHub-synced values.)
- Add an edit button to the https://nest.owasp.org/members/anirudhprmar view and a top nav bar option which will display the profile with the edit button > which will be a form that user / contributor can update

So finally the working feature will allow :
Contributors to edit information like their username (not sure will this be needed), location or their github stats or even their contribution chart

**Are you going to work on implementing this?**

- [X] Yes
- [ ] No

Start by reading the github_users data model, the GraphQL API and mutation, and the contributor member page at /members/anirudhprmar, then inspect the top navigation entry point. Define the editable profile fields and fallback behavior before implementing the form; done means contributors can update the agreed fields and see the resulting profile values.

Written by the indexing model from the issue text.