[no-Jira] Sort import statements and members

[canac]

Description

Standardize import order. react first, then all libraries, then imports from the root directory, then parents, then siblings.

I only made changes to .eslintrc.js and ran yarn lint until all errors were fixed, so you shouldn't necessarily need to manually review every changed line.

@dr-bizz Do you have any suggestions or improvements to this sort order?

Checklist:

• I have given my PR a title with the format "MPDX-(JIRA#) (summary sentence max 80 chars)"
• I have applied the appropriate labels. (Add the label "On Staging" to get the branch automatically merged into staging.)
• I have requested a review from another person on the project

[aws-amplify-us-east-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-829.d3dytjb8adxkk5.amplifyapp.com

[dr-bizz]

Great wortk on this!! Thank you for doing this!.

I did wonder if we should also include next straight after react, as Next is such a key part of this repo. What are your thoughts?
I'll approve the changes anyway as it looks good.

[canac]

@dr-bizz I can see a case for that and will move next to the top. Should we keep next-auth where it currently is? That's what I lean towards.

[dr-bizz]

@dr-bizz I can see a case for that and will move next to the top. Should we keep next-auth where it currently is? That's what I lean towards.

That sounds good to me. Thank you!