Port email_example module to Drupal 8

Rock on, pferlito. :-)

Nice start. Just a few things...

1. +++ b/email_example/email_example.info.yml
   @@ -0,0 +1,6 @@
   +package: Custom
   +version: 8.x-1.0
   

   package: Examples

   and

   version: 8.x-1.x

2. +++ b/email_example/email_example.module
   @@ -0,0 +1,164 @@
   +///// Supporting functions ////
   

   We want to avoid these kinds of comments. Put documentation in the docblocks so api.drupal.org can find them, or inline with the code so people can read them.

3. +++ b/email_example/email_example.module
   @@ -0,0 +1,164 @@
   +function email_example_menu() {
   +  $items['/examples/email_example'] = array(
   +		'title' => 'E-mail Example: contact form',
   +		'description' => 'Callback for generating form.',
   +		'route_name' => 'email_example',
   +    'type' => MENU_NORMAL_ITEM, // Default.
   +	);
   +  return $items;
   

   Spaces not tabs. :-)

4. +++ b/email_example/lib/Drupal/email_example/Form/EmailExampleGetFormPage.php
   @@ -0,0 +1,62 @@
   +  /**
   +   * {@inheritdoc}
   +   */
   

   Examples is more of a documentation project than a code one. We want to explain the hows and whys of implementing stuff, so as a rule of thumb, @inheritdoc should be replaced with 'We're overriding this method because....'

Also, no tests. Even a functional SimpleTest to make sure the module can be enabled without blowing up would be good.

Thanks.

#8: email_example-2102621-8.patch queued for re-testing.

Updated issue summary.

@pferlito: Thanks for the patches!

What is new in this patch:

• Replace Implement with Implements on hook implementation comments.
• drupal_mail() expects langcode, no language object.
• Update documentation to reflect new way of retrieving the language codes.
• Do not use deprecated functions.
• Minor formating errors.
• Improve test to reflect most of what D7 was doing.
• Added defgroup end block.

I will add this after testbot agrees.

Mail example added!