package content bootstrap module in shared/lib (was: conditionally)

A best practice in PS for avoiding that production data gets overridden by bootstrap content is to put all bootstrap resources that should only be applied locally into the "content" bootstrap module, and only build/package it locally. This is achieved by a "local" maven profile, which adds the bootstrap/content module to the CMS dependencies.

I consider it a desirable improvement to make this profile / mechanism available as a default by including it in the archetype.