Converting Projects to Work with Master Build 4811 and Later

A list of model changes we had to do to move a major project:

- Rename CZ.Advantages.Asap -> Origam at model
- Inspect stored procedures, they can have 'AsapListValue' datatype used, rename
- Inspect stored procedures, can have some references to asap tables
  - e.g. BusinessPartnerAsapRole
- Make role names non-asap:
  UPDATE [OrigamApplicationRole] SET [Name] = REPLACE([Name], 'Asap', 'Origam')
- In any UpdateContextTask if the input value xpath context store is scalar,
  the /ROOT/Value has to be used to get the data from (was '/' before)
- The longest path at the filesystem has to be 255, make names in model shorter
  if this is applicable (the actual conversion to filesystem would fail). Or
  other solution is to remove a limit (must be configured at windows and can't
  be taken back). 
- All parameters in all APIs became case sensitive. So it could happen some
 client doesn't use the correct spelling. Fix either on client ot API side.
- Correct model errors - new architect checks all model inconsistencies and
 report them on package opening. It's worth to fix those inconsistencies.
- API - endpoints are now scanned for duplicates, check that there aren't
 any duplicates. It returns the 404 in that case. Before, the first (random)
 handler was used.
- For-each block with _any contexstore doesn't work stable
  - ignoreSourceContextChanges must be set
- Mailing doesn't work - all notification templates must have <OrigamNotification>
  element instead of <AsapNotification>. 
- API endpoints: origam is more sensitive about returned mime-type and started
 not to return error (RuleResult) in json if the services  wasn't application/json
- Handle the situation where a child entity of another entity is a root entity
 in screen's DS - in that situation since master-september-2018 it cheks row
 level security rule for the creation by adding a new empty testing record. We
 have to handle this situation when no refParentEntityId is present
 - disable creation.
- Incorrect conversion of XslRule (rules that are just old library rules used
 only as an xsl:inc- must be converted to EndRule. (Some xsl rules
- HTML: convert all transformations from XslTransform to XslCompiledTransform.
 XslCompiledTransform is more strict about an error when a productd output
 contains attribute nodes after subnodes has been already added.
- HTML: check lazily loaded screens - in lazily loaded screens, the list
 datastructure must include all the columns used in a master screen section
 of the screen. (Flash was less strict)
- HTML: change ReloadActualRecord->RefreshCompleteForm in some cases - Flash
 used to reload the form even when 'ReloadActualRecord' was set at some cases.
- HTML: external assemblies with custom service agents (not known at compile
 time) has to include a version of assembly to access it (at the model). E.g.
 "Com.Customer.Project.ProjectService,Com.Customer.Project,Version=1.0.0.0"
- Output of complex datastructure rule must output <ROOT> element now. Old
 version was less strict and could work even without it.