Use markdown for stable references to software tools

[interim17]

Use Case

Tools might be referenced in several issues. Having markdown pages for those write ups would be useful.

If a given set of data doesn't need it's own page to be built out by gatsby, we should configure gatsby to ignore those templateKeys.

Acceptance Criteria

• /pages/software exists and defines some usable data
• config.yml reflects the new changes
• gatsby doesn't build out those pages/end points
• React has matching interfaces and working queries

Details

Please provide any helpful specifications

[interim17]

@meganrm in working on building out the single "page" I found some changes I would like to make to some of the data structures and configuration.

This issue and the two open PRs are the bulk of what I'd like to do that doesn't fall strictly under the auspices of "build out the page". The rest of the work should be more straightforwardly presentational.

Lmk if you think this is out of scope, or you would do it differently. My experience working this gatsby/decap style on cell-catalog teaches me that its nice to get these data structures and configs in a place that we like them before we have too many components and queries actually referencing the data.