Available languages field for Nodes

Added it as a seperate module, since not all sites have multiple languages and therefor don't need this field. The availableLanguages field has a language and url field, but can be extended if needed.

One possible improvement would be to add this to the node interface instead of individual bundles.

would this be something like what happens in graphql_compose_metatags?

I like this. I also like the idea of expanding the generalness of languages on the site.

Possibly:
- Add a LanguageCode emum (or similar)
- Add languages to info query
- Add (translations) as a field to translatable entities.
- Add an interface to translatable entities to introduce the new field
- Make that return an array of the enums
- Alter Languages.code to use enum value.

I might stab at this a bit in another MR

I uh, did some things.

Check out dev, should be there :)
I didn't add it to the NodeInterface, as you can enable and disable translations per bundle.

I also pulled back some schema if a site is not multi lingual, eg no need for langcode queries on nodes etc.

Shape of data should be:

  node(id: "ccc6baa9-1545-4332-ac48-daedb146dd6a", langcode: "en") {
    ... on NodeInterface {
      title
      langcode {
        id
      }
    }
    ... on NodePage {
      translations {
        title
        langcode {
          id
        }
        url
      }
    }
  }

Changing `url` to `path` to match parent entity pattern.

As it's merged, marking as fixed. Will release into beta 2 in prep for RC.

almunnings → closed merge request !67

Beta 2 tagged, thanks all

Great!