Make sure new binaries replace existing binaries in docker-sonic-vs

PR #716 removed a step where existing deb packages were removed before
installing the new deb packages. The problem is that due to Docker's
change detection code, where it only checks the file size and the
modification timestamp, even if the file gets modified when installing a
newer debian package, the file size may remain the same, and the
modification timestamp will remain the same (since this is based on the
debian/changelog timestamp). This caused changed binaries to not
actually replace the existing binaries.

Fix this by re-adding the line that removed existing packages first.

Signed-off-by: Saikrishna Arcot <[email protected]>

.azure-pipelines/docker-sonic-vs/Dockerfile

@@ -4,4 +4,8 @@ ARG docker_container_name
 
 COPY ["debs", "/debs"]
 
+# Remove existing packages first before installing the new/current packages. This is to overcome limitations with
+# Docker's diff detection mechanism, where only the file size and the modification timestamp (which will remain the
+# same, even though contents have changed) are checked between the previous and current layer.
+RUN dpkg --purge libswsscommon python3-swsscommon sonic-db-cli libsaimetadata libsairedis libsaivs syncd-vs swss
 RUN dpkg -i /debs/libswsscommon_1.0.0_amd64.deb /debs/python3-swsscommon_1.0.0_amd64.deb /debs/sonic-db-cli_1.0.0_amd64.deb /debs/libsaimetadata_1.0.0_amd64.deb /debs/libsairedis_1.0.0_amd64.deb /debs/libsaivs_1.0.0_amd64.deb /debs/syncd-vs_1.0.0_amd64.deb /debs/swss_1.0.0_amd64.deb