Investigate and potentially remove running caliper unit tests on a merge

[davidkel]

A merge performs a run of the caliper unit tests before performing the publish. I'm not sure why this is done, would be good to find out and document or remove if not necessary to reduce the build pipeline time

[davidkel]

From Attila: Probably it was due to a reasoning like "they're cheap and couldn't hurt" :D although pr unit tests aren't run again automatically when a separate pr is merged (thus the upstream changes), so the test after merge ensures that the published codebase still works as intended I guess

I think this gives to good reasons to keep the unit tests on PR merge, so closing