Replace "Snapshot" on Releases page for projects with per-release field

Most of these strings are in this module. I agree they should be changed.

Let's expand the scope of this. With semantic versioning, there is not necessarily one dev release per API compatibility of the project. For example, core's 8.1.x and 8.0.x.

This functionality can be replaced by a field on the release node itself.

• If dev, label as “Show in project’s download table when branch is supported” to match current behavior.
• Else if stable, hide the field (for now, may have future use)

We'll need an update script:

• Add the field
• For each dev release
• • Default to 1
  • If on supported branch, and not shown, then 0
  • Use hacky save to avoid updating timestamps and triggering packaging

Adding the field has been committed to a branch. For the rest of the update script:

"hacky save" as in http://cgit.drupalcode.org/drupalorg/tree/drupalorg_project/drupalorg_pr.... I'm not sure how much this is abusing Drupal's APIs, but it seems to work and isn't calling private functions.

The data from project_release_supported_versions's snapshot column should be copied over to the new field.

Hiding the field on releases where field_release_build_type is static can be done in project_release_field_access.

The remaining work is:

• Update the download table View.
• Remove the Views handling of this column.
• Remove the column, followup after we know the data can go.

I think everything for this issue is handled, the Views work has been committed and I opened #2626694: Cleanup: remove project_release_supported_versions.snapshot column for cleanup.

This has been deployed to Drupal.org.

Snapshots are not releases. Ok, they are not done nightly only, but they are still snapshots of possibly totally unstable states that may change every few minutes with every commit.

Dev releases I think "development release" is accurate. It is a release, and development or dev is the term used everywhere except for these corners of the UI that were inconsistent.