[FieldTypes] Trying to link ValueTypes and new FieldInfo hierarchy of types.
- Not sure if this will work out yet
- Must find a way to reduce duplcation of concepts
- Commented out TermSetInfo and TermGroupInfo child entity (terms and term sets, respectively). If you need such information, perhaps it's best you fetched the full information from the ITaxonomyService anyway... An *Info object should hold only the minimally functional serializable version of its corresponding server-side API object. Right now, we don't need the child entities, so let's not put them in.
- Introduced TaxonomyContext and TermStoreInfo (trying to find a way to get rid of TaxonomyFieldInfoValue)
[FieldTypes] Getting rid of IFieldInfoValue in favor of TaxonomyFullValue.
- Eventually, TaxonomyFullValue could also replace the good old TaxonomyValue. For the time being, while we get the converters sorted out, let's keep them separate.
- TermGroupInfo and TermSetInfo have their parent in their properties, instead of listing their children. Thanks to this, from TermInfo you can navigation all the way up to the TermStoreInfo object.
- TaxonomyContext takes care of summarizing this ParentTermSet -> ParentTermGroup -> ParentTermStore chain AND also it documents the TermSubset limiting term (optional) parameter (to limit choices under a specifc term in the term set)
[FieldTypes] Split up TaxonomyMultiFieldInfo from TaxonomyFieldInfo and NoteFieldInfo from TextFieldInfo.
- Got rid of Definitions.Values namespace
- Validating in FieldInfo constructor that InternalName doesn't go over 32 char max length
- Removed redundant ToXElement which gets taken care of by Schema property.
- Removed a few settings on IFieldInfo properties to force people to use the non-default constructor (and thus avoid partially initialized FieldInfos)
- Initializing ListInfo collection properties with empty lists to avoid NullRefExceptions
[FieldTypes] Added some starter unit tests for TextFieldInfo
- Opened up the TitleResources and DescriptionResources can of worms. Now using ResourceKey properties instead everywhere. IResourceLocator should be used instead of storing all resources AGAIN in the BaseTypeInfo <CultureInfo, string> silly dictionaries.
- ListHelper and ContentTypeHelper now use the SupportedUICultures on the SPWeb to figure out which resources to set. Couple of nasty signature changes.
- Introduced MinimalFieldInfo for BuiltInFields because I couldn't bother to document them all (with Type, displayName, description and contentGroup as well?! - ugh, no thanks! :D)
- Added InternalServiceLocator to gain access to IResourceLocator for computed DisplayName, Description and Group properties in BaseTypeInfo. Hopefully this will work out... wish I could figure out a way to not service locate within the core Dynamite lib (this is the first instance of such core service location - bit smelly!)
[TextFieldInfo] The first proper test class' unit test all pass.
- Getting SPDiagnosticsService and SPMonitoredScope to not explode during a test run has proven to be difficult. We'll need to come up with an abstraction for SPMonitored scope at least...
- Note that these unit test don't run in much isolation and that the InternalServiceLocator scans the GAC to find a proper service locator and registration modules.
[NoteFieldInfo] Unit test, very similar to TextFieldInfo.
- Watching out for RichTextMode="FullHtml/Compatible"
[FieldTypes] Added a bunch of new FieldInfos.
- Url, Html, Image, Lookup+Multi, User+Multi, Number types
- Added missing UserValueCollection and LookupValueCollection, still missing the corresponding Mult-type field value converters
Merge branch 'feature/v2.0_value_and_field_types_unification' into develop.
Obsoleted the Setup namespace which will be gradually replaced by the Definitions and Helpers (namespaces need to be reviewed).

Conflicts:
	Source/GSoft.Dynamite/Definitions/GuidFieldInfo.cs
	Source/GSoft.Dynamite/Definitions/TextFieldInfo.cs
	Source/GSoft.Dynamite/GSoft.Dynamite.csproj