Replacing TS any by unknown, as using any is highly NOT recommended

[cassiano]

Replacing TS any by unknown, as using any is highly NOT recommended

Changes:

I have verified that this pull request:

• has no linting errors (npm run lint)
• has no test errors (npm run test)
• is from a uniquely-named feature branch and is up to date with the develop branch.
• is descriptively named
• meets the standards outlined in the accessibility guidelines

[cassiano]

@raclim, you might want to check with your dev team if they agree with my proposed changes. I personally NEVER use any, unless under some very exceptional circumstances.

[raclim]

Thanks for the suggestion!

Will tag @clairep94 and @khanniie to chime in on this, since they have been leading the TypeScript migration work!

[khanniie]

if typechecks pass idm merging it in! defer to @clairep94 on if she had a reason for using one over the other, i recall we may have had a conversation on a PR about using any but i forget if it was about this particular case and were we ended up on it