Code review comment for ~eslerm/ubuntu-cve-tracker:select-reference-refresh

Yes.

This merge request reflect tooling updates for generating UCT file metadata. Since making this merge, feature requests to lint urls (references, bugs, patches) have caused refactoring that tooling, still WIP.

Afterwards, I will stage `--refresh` updates to UCT. (i.e., My tooling lints whitespace in descriptions slightly differently (better?) and I will make a commit of just refreshing UCT's description. Another commit will include just new launchpad bug references and so on.) The thought is that each update should be isolated in a commit for review.

As it stands, once new tooling is ready I would reset this branch to master and begin layering update commits. If preferred, I could close this merge request and make a new one later.