Add dependency notes file

[mint-thompson]

Description:
Adds the dependency notes file to track dependencies that are intentionally left out of date. All dependencies are currently up-to-date, so there are no dependencies listed in the file.

Related Issue:
Fixes #35

[jafeltra]

Small question. It looks like moment is on v2.30.1 and the package-lock.json has already been updated to use that version. Are we trying to keep the package.json list updated with the latest versions we're using as well? If so, we can update that file. On the other hand, package-lock.json is doing what it is supposed to do, it probably isn't a huge deal either way.

[mint-thompson]

Small question. It looks like moment is on v2.30.1 and the package-lock.json has already been updated to use that version. Are we trying to keep the package.json list updated with the latest versions we're using as well? If so, we can update that file. On the other hand, package-lock.json is doing what it is supposed to do, it probably isn't a huge deal either way.

I think it's okay? npm outdated does not seem to ask for anything to be changed, so it should be fine.

[jafeltra]

I think it's okay? npm outdated does not seem to ask for anything to be changed, so it should be fine.

Yeah, that's why I wasn't sure if we needed it. But the package.json lists moment version 2.29.1, but the latest version is 2.30.1. In the other PRs, we've been updating that version in the package.json, rather than just in the package-lock.json, which is why I asked about doing that here as well. But if you don't think it's necessary, then that's fine with me.

[cmoesel]

Yeah, I think it's technically OK. It's kind of nice when the package.json reflects the latest as of the time you did the updates -- but it's not necessary. There are probably other cases in our other packages where this happens but it's not as obvious because there are so many more dependencies in those ones.

[cmoesel]

Easy peasy. Thanks Mint!