Use jsdoc rules recommended for typescript

[spearec]

Description

Merging #949 caused a few issues with jsdoc, and while resolving those I had a look through the package documentation. There is a specific recommended ruleset for typescript, which is different from what OED was using. This ruleset removes the need for types in jsdoc headers, as they are redundant since typescript is a typed language.
I also took the chance to use eslint overrides to disable jsdoc as a rule for actions, reducers, and containers, instead of disabling jsdoc on a per-file basis. This allows easier control over the rules for these files as a group.

Type of change

(Check the ones that apply by placing an "x" instead of the space in the [ ] so it becomes [x])

• Note merging this changes the database configuration.
• This change requires a documentation update

Checklist

• I have followed the OED pull request ideas
• I have removed text in ( ) from the issue request

[huss]

Thanks to @spearec for quickly updating the files based on the recent update to eslint. I know removing all those recent edits was painful so I am esp. grateful.

I've made a couple of comments but overall this looks very good. Note I added a comment in issue #726 so the TODOs in .eslintrc.json will be addressed.

[spearec]

As other comments, return the JSON structure if we are doing that.

In this case, the JSON structure is directly noted in the function header instead of an interface, so the mouseover text of the function has the structure.