Fix composite namevars on wls_subdeployments

Edwin,

I've looked into the composite namevars and easy_type. Looks like your implementation doesn't work consistently. I've changed it. The idea's behind it are:

- The name **MUST** be available in the type and it **MUST** be an unique identifier of the resource.
- Using `to_translate_to_resource` you **MUST ALWAYS** translate the raw resource attribute `name`
- The other `namevar` attributes **MUST* be defined, but they **MUST NOT** have a `to_translate_to_resource` method. There content will be filled using `title_patterns`
- Using `self.title_patterns` you can fill in any of the other `namevar` attributes 

Can you check the other composite namevars as well for this methodology?

Thnx