utilize more types in LFNext

[longrunningprocess]

Description

This PR begins to utilize types more extensively in the LFNext app.

Type of Change

• Tooling update

Checklist

• I have labeled my PR with: bug, feature, engineering, security fix or testing
• I have performed a self-review of my own code
• I have reviewed the title & description of this PR which I will use as the squashed PR commit message
• I have commented my code, particularly in hard-to-understand areas
• I have enabled auto-merge (optional)

How to test

• exercise the change password feature
• exercise the project dashboard feature
• exercise the menu option while on any of the LFNext pages
• there was a change to the way the number of entries with pictures and audio is calculated so those numbers should be checked closely to ensure their accuracy.

qa.languageforge.org testing

Testers should add his/her findings to end of the PR in a comment and include screenshots, files, etc that are beneficial.

[hahn-kev]

It looks good to me. The only thing left that we discussed was throw_error, right now it only accepts a string, but in fetch we're potentially passing it an error object when there's a network error and throw_error should be updated to indicate that it accepts an Error object.

[myieye]

I appreciate you putting the time into this 🤓. I mostly just have a few ideas. Feel free to use or toss whichever you wish.

[myieye]

QA 🧪

✅ exercise the change password feature
✅ exercise the project dashboard feature
✅ exercise the menu option while on any of the LFNext pages
💥 there was a change to the way the number of entries with pictures and audio is calculated so those numbers should be checked closely to ensure their accuracy.

We decided that there's nothing critical enough here to stop the release, but there is some work to be done. So, I've created #1690