(cherry picked from commit 7c6c97b1e8bc9672e13c2da32eab91afd0d9c91d)

Conflicts:

	htdocs/theme/raw/templates/group/membersearchresults.tpl
	htdocs/theme/raw/templates/group/view.tpl

View.

This means that blog/profile/resume blocktypes don't show up in
group/institution/site Views.

This is controlled through a new Blocktype method - allowed_in_view.
Various code had to be changed to listen to this method, mostly around
the display of the category browser.

When making a template, all blocktypes are available.

Part 3 is to change the configuration forms to be more sensible when
editing a template, and then testing what happens when blocktypes are
rendered somewhere that they "shouldn't" be - e.g. a My Friends block in
a group View.

beginning of wall and another backwards compatibility break for blocktypes now we must pass $editing parameter to render_instance (default false)

 needs implementing in view/block edit frontend.

More work on profile views and three new blocktypes (myfriends/mygroups/myviews) to emulate current profile page TODO: - write wall blocktype - change install default profile view hook to add blocks - upgrade path (xmldb & migration) - blocktype and category and singleblockperview implementation

    - TESTING