VMware.PSDesiredStateConfiguration introduction

[KristiyanGK]

Added

• Introduced a new module VMware.PSDesiredStateConfiguration for compiling and executing DSC Configurations without the use of MOF or LCM.
• Added separate documentation files for both modules (VMware.PSDesiredStateConfiguration.md and VMware.vSphereDSC.md).
• Added EnableExperimentalFeature.ps1 to enable Invoke-DscResource cmdlet on non-windows Operating Systems.
• Added a documentation file: Limitations.md for listing known issues and limitations.

Changed

• Updated the build procedure in build.ps1 to now work with both modules (VMware.PSDesiredStateConfiguration and VMware.vSphereDSC).
• Updated README.md with common information and links to the new documentation files for both modules (VMware.PSDesiredStateConfiguration and VMware.vSphereDSC) .
• .travis.yml now works with both Ubuntu 14.04 and Ubuntu 18.04 due to Ubuntu 14.04 not supporting Powershell Core 7.0.3.

[vmwclabot]

@KristiyanGK, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit c87f5817f50abffb717021b314f228007c52e316 must be signed by kristiangk@abv.bg

[vmwclabot]

@KristiyanGK, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <john.doe@email.org> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit ae560c10f7de0ddb9d15ea210474b446c3511af0 must be signed by kristiangk@abv.bg

[KristiyanGK]

Do we have insurance that the flow of the build (with the different stages and workspaces) is executed in the order that is defined in the .travis.yml ?

Yes, the build must execute in the order defined in the .travis.yml.