Missing profile part

[wbloszyk]

Reference to #614 #547

Subject

I add SonataProfileBundle - copy of missing part when update SonataUserBundle 3.x to 4.x.

I am targeting this branch, because it is feature with BC.

Changelog

### Added
- Added missing profile part when using SonataUserBundle > 3.x

[wbloszyk]

For now ProfileBundle is copy of missing profile from SonataUserBunde < 4.0. Base on #1121 SonataUserBundle should only integrate User to Admin, without frontend. Also ProfileBundle is not required in ecommerce bundle(but nice to have in sandbox).

This bundle have:

• simple user block
• menu block
• profile component

Lets make new secound tier bundle with predefined block, components, tools etc., which is "Nice to have" in sandbox and other system, but is not required. By default should be disabled.

List what it can have:

• simple user block,
• menus tools with menu block (to define many menus)
• breadcrumb tools (simmilar to menu, also can be generated from menu)
• profiles components
• newsletter (block to display, controller to handler and events where developer can add what to do)
• newsletter in admin (to send email to subscibers)
• and many others

@core23 @greg0ire
Mybe SonataToolsBundle? Or I should close this PR and replace this code to sandbox?

[core23]

So the whole profile stuff is not related to the ecommerce bundle at all? We'll create a new repo for this the next days

[wbloszyk]

@core23
before ecommerce used profile from UserBundle. Now they should have own minimal profile(not editable) which can be override by seperate profile bundle.

[wbloszyk]

So the whole profile stuff is not related to the ecommerce bundle at all? We'll create a new repo for this the next days

@core23 new repo or bundle for one feature is not enought. I resolve profile(dashboard) issue by add template and menu_builder variable to configuration. Now ecommerce have own profile, like UserBundle should have. Also profiles can be easy merge by change menu_builder options.