Add a filter type for the release status

Right now we do have a filter of "recommended" or "all" - which isn't quite the granularity here that I think is being asked for. However, I'm not convinced we need/want this level, if we're considering our main target audience are site builders and those new to Drupal. I tend to think the current filter set is adequate, unless someone can point me to some data or research suggesting otherwise.

hm back then we were under the impression that it would be possible at some point for the user to decide which version of a module to install within the project browser interface. for example if a module has version 3 as stable and version 4 in beta or alpha a user would be able to exclude the version 4 in beta or alpha since the person only wanted stable releases. that way a filter would made sense. but the user never actually sees the version number of a to be installed module until the install process is finished. therefore i am not sure if such a filter would make sense anymore and in contrast wouldn't lead to further confusions. if you as the user are unable to choose the to be installed version of a module but you have a filter type enabling you to filter for those exact criteria? i would consider that confusing tbh.

Presently, the issue is that we're leaving it up to Composer, more or less, to determine what version of a module should be installed - based on what's in your composer.json (i.e. the settings of "prefer-stable" and "minimum-stability" specifically). Since we're not surfacing _that_ configuration to the user (i.e. they can't change those settings in composer.json from the UI), it doesn't make a lot of sense to have them attempt to specify a version. (I could see this happening someday, though.)

I wonder what the minimal increment is that resolves the UX concern - would it be showing the installed version number once it completes? Or before, as a confirmation?

I'm not in favour of this change, mostly I agree with #6. A few people have pointed out that the meaning might be lost on the target audience, and I must admit even I was not fully aware of the 'full release' terminology. I knew what it meant, but I stopped and thought 'wait is that really what we call it?'

I also don't think the difference is all that meaningful in contrib, as every module maintainer has a seemingly different definition for what is alpha/beta/RC etc. I think it would be an easier sell if there were consistency. It is a long list of options, with honestly not that much distinction and therefore not that much value to the user.

OK, great. I think that was a consensus needed. This will not be in MVP, but we can also look at revisiting it if it causes confusion after a larger-scale release.