Fix Privacy Guard unit test failures

[zgzjhzxhq]

This change fixes Privacy Guard related unit test and functional test failures.

1. one unit test failure that fails 1/3 of the time due to a probabilistic issue.
2. one unit test failure due to test code out of date with production code
3. one functional test failure due to test code out of date with production code.

They were not discovered earlier because some of the test cases are not run in 1DS C++ SDK main repo build pipelines - privacy guard is in submodule repo, so main repo does not compile them along with public SDK files, hence some unit tests are disabled using a macro.

I discussed with Lalit and the agreement we settled is that developers need to run all unit test locally before submitting PR for review. I also modified our developers guide to include this in Privacy Guard team guide.

[lalitb]

Thanks for the fix.

[lalitb]

MacOS CI tests are not running for #1299, we should be good to force merge to unblock privacy guard CI.

[ThomsonTan]

Does this apply to the privacy guard module, or all modules for cpp_client_telemetry?

the agreement we settled is that developers need to run all unit test locally before submitting PR for review.

[zgzjhzxhq]

Does this apply to the privacy guard module, or all modules for cpp_client_telemetry?

the agreement we settled is that developers need to run all unit test locally before submitting PR for review.

It is for the privacy guard module in 1DS C++ SDK only. Similar situation may apply to other components in the *_modules repo, though, it's up to them whether they want to do the same.