Adding vcpkg to cpp image definitions

[dnastrain]

#781

Description

---

This PR adds:

• Updated base.Dockerfile to add support for Vcpkg c++ package manager
• Updated Dockerfile to support conditional CMake re-install from an official release
• Updated tests to verify Vcpkg is present and configured, when supported
• Updated README.md documentation

PR Checklist

---

Use the check-list below to ensure your branch is ready for PR. If the item is not applicable, leave it blank.

• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My code follows the code style of this project.
• I ran the lint checks which produced no new errors nor warnings for my changes.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.

Does this introduce a breaking change?

---

• Yes
• No

If this introduces a breaking change, please describe the impact and migration path for existing applications below.

Testing

---

• test-project/test.sh updated to ensure Vcpkg is configured and can run vcpkg --version
• rebuilt the distros supported according to definition-manifest.json
• ensured scripts invoked by the 2 Dockerfiles worked on supported distros.

Other information or known dependencies

---

NOTE: Due to vcpkg constraints running on arm64, vcpkg is not installed on arm64 stretch and bionic distros

[dnastrain]

hi @Chuxel , this is ready for review. (cc:@bderusha)

[Chuxel]

A few questions/comments.

[bderusha]

@Chuxel Changes made based on your feedback. Ready for another pass when you get a chance.

[bderusha]

Also, since you asked about it during the design review we wanted to just confirm for you that the base image size increases from 1.45GB to 1.50GB with this change.

[bderusha]

@Chuxel do we also need to update the definition-manifest at all given the new package dependencies the install-vcpkg script adds on some base images (all but stretch and bionic)? I don't know enough about how that file gets used to determine on my own. Let me know what you think :)

[Chuxel]

@Chuxel do we also need to update the definition-manifest at all given the new package dependencies the install-vcpkg script adds on some base images (all but stretch and bionic)? I don't know enough about how that file gets used to determine on my own. Let me know what you think :)

@bderusha Yeah that would be a good idea for anything that ends up in the image. Packages installed from apt from the main distro are covered by registrying the distro (which is already done). 3rd party dependencies, however, should be added. cmake we can just use the version that is installed... worst case we register one we're already covered by.

Otherwise LGTM!!

[bderusha]

@Chuxel Updated the definition-manifest.

[dnastrain]

@Chuxel Updated the definition-manifest.

Thx @bderusha ! We think this is ready to merge @Chuxel -- please let us know when you have the cycles.

[Chuxel]

LGTM! Merging!