I don't know the answers to these but I'm thinking about them now...

For packaged apps that have multiple versions... if I have my app and version features tied to version 1.0 and upload version 2.0 which is still pending review, the edit form is going to show the features tied to version 2.0 b/c it's the latest version.

On uploading version 2.0 am I presented with the app features form again to check which features my new version requires? If so, do we default to the prior version's features being checked off (which seems friendly)?

If version 2.0 now requires MMS (e.g.) but version 1.0 didn't, I would think we don't want to "activate" the version 2.0 feature requirements until it is published. Which means this devhub edit form should use `current_version` which is the latest published version. At least I think it should otherwise we might as well put the `ForeignKey` on the `addon` table and not track them against `version`. But if version 1.0 doesn't require MMS and my device has no MMS I'd still want to be able to search and install it before version 2.0 is published, which means we need to be careful how we handle this.

This is kinda ugly and painful.