Implement dynamic UI for all current service creation forms.

1. Show only selected service description in Create Service step0
form.

2. Move template names and params postprocessing into service forms.

3. Move all forms post-processing (before passing to api) into
declarative specs. All post-processing is actually performed in
extract_attributes form functions according to attributeNames
attr. for each field in each form.

4. Support generation of multiple forms (steps) from one service
definition.

5. Dynamic forms UI use services yaml-description.

6. Use predefined field types instead of eval-ing python object
names. Also use camelCased names instead of pythonic_ones.

7. Localize string values for predefined keys and do not use string
prefix.

8. Add verify password fields automatically for each password field.

9. Use attributeNames for each field description instead. Value of
attributeNames can be:
* list - field value will propagated to multiple attributes;
* omitted - field value will be propagated to attribute with same
  name;
* false - field value won't be propagated to any attribute;
* string - field value will be propagated to attribute whose name is
 specified by the string, with one note: `attributeNames: domain.x'
 for field `A' will produce attribute value `domain: {x: A.value}'

10. Remove django template from service description. Use per-field
descriptions. If the field in service's description has attribute
`description', it is automatically inserted into appropriate form
description. If `descriptionTitle' attribute is present, it becomes
the title of field description, else `label' attribute is used.

11. Also in addition to an existing regexp literal (quoted string) add
new one: quoted string with slashes: '/some-regexp/flags'. Flags is
split into list of 1-letter strings <flag>, each of them is uppercased
to <FLAG> and sent to re.compile as getattr(re, <FLAG>).

Change-Id: I76c25cbbd682823cbef2693b51ccd69ffe83b6d4