Resolve Circular Dependency

[afischer]

Description of Change

This PR removes some longstanding circular dependencies in the app without modifying app behavior. It also rearranges some tests to better reflect the new location of these dependencies.

I believe server/list.js > server/docs.js > server/formatter.js is causing the issues, but eventually we should work towards getting rid of all of them.

Cycles to resolve:

Detected via npx madge --circular .

• server/cache.js > server/urlParser.js > server/list.js
• server/cache.js > server/urlParser.js > server/list.js > server/docs.js
• server/list.js > server/docs.js > server/formatter.js

Related Issue

Towards #361

Motivation and Context

With the release of v1.5.0, this bug could cause headaches for users after upgrading.

Checklist

• Ran npm run lint and updated code style accordingly
• npm run test passes
• PR has a description and all contributors/stakeholder are noted/cc'ed
• tests are updated and/or added to cover new code
• relevant documentation is changed and/or added

[isaacwhite]

Makes sense to me! It probably is best for us to eliminate these circular dependencies to the extent that we can, but will mention that previously the way we avoided most of the runtime errors was by deferring the destructuring until just before the functions were needed.

That usually gives Node the time it needs to fully evaluate files on both sides of the import, so that all properties have been defined (so long as module.exports hasn't been reassigned)