App version with no routes json (bc error) needs to treated as unusable

[teleclimber]

Scenario:

• new app code acquired
• DS runs router to get routes json
• Error occurs, or maybe returned json is incorrect
• App version needs to be treated as flawed an unusable

DS needs to keep track of whether an app version is satisfactory and ready to use or not. Although there is no reason to stash this in DB? all this can be determined quickly after acquiring app code.

On the flip side, we need to consider what might happen if a new version of DS is no longer able to use the app version? Like a change in API or a change in deno std lib might now result in errors?

Unclear how to proceed.

[teleclimber]

Likely that #23 should be fixed when this is being worked on.

[teleclimber]

For now this is fixed enough because apps that error during app get processing don't make it to the usable stage. Later we may run into situations where an app that was working can no longer work because of changes, but that seems like something we should avoid altogether.