rip out bizarre "default version" behavior

actually, the problem is that there's some weird, legacy code in here so that if you try to submit an issue with a version of [none], it'll automatically submit it with the "default version", instead.

if this feature ever made sense, the default should have showed up as a #default_value in the form in the first place.

however, there's no longer any reasonable "default version", since it depends on the branch, core API, etc, etc.

i think all this code should go, so that in validate(), if we're still at [none], we should mark it as an error, not silently set the version to something else.

this is really a bug, not just a task, since $project->version is no longer controlled in any way. it's just stale info in a (should be) unused column in the {project_projects} table that might as well be dropped (the 'version' column, that is, not the table). ;)

DRUPAL-4-7--2 version

DRUPAL-4-7 version

This makes sense to me. It was unexpected behavior for hunmonk and I think it makes more sense to force the user to choose the version than to just default it.

greggles agreed this was stupid, so i killed it. applied to all 3 branches.