Support attributes with attribute type COMPOSITION about frontend

[IskandarovRost]

Test-cases(for exploratory testing):

1. One-to-one composition. Owning side. Check when the nested entity is persisted. Cancel, edit.
2. One-to-one composition. Not owning side
3. One-to-many composition. Entity with or without Instance name.
4. Should the user manually create CRUD - components for details?
5. Check also what is difference with association attrib
6. Details with undefined instance name
7. Is there Paging in the list of nested Details(on master-edit component)???
8. Which actions are available in the list of (many) details? Try to create, edit, remove. Is There "add" or "exclude"?
9. Master with several composition attributes

[IskandarovRost]

Created Studio feature: https://youtrack.haulmont.com/issue/STUDIO-8452 "Composition attributes when creating Frontend components"

[IskandarovRost]

(As improvement) No need to create editor for the nested entity if _local was selected for the edit-component.

Created the issue #212

[IskandarovRost]

(problem) New Master and List of details could not be persisted together (One_to_many composition)

Created the issue #213

[IskandarovRost]

(problem) When an entity has several composition attributes only one of them is presented on edit-component

Created the "enhancement" #214

[IskandarovRost]

All the problems and improvements posted to separate issues. Closed.