Support subfields/columns mapping by default

Currently CCK fields that have multiple columns in the database need a special mapper to be able to be populated (date, link, emfield etc). That makes sense if there's special considerations for whatever data processing needs to be done.

However, if there's a custom CCK field which simply has several columns in the database, those should be exposed for mapping by default unless overwritten otherwise.

Patch will follow...