Use a unique version for plugins

[dominiklohmann]

📔 Description

This changes plugin versions to be set automatically by the VASTRegisterPlugin CMake function. A plugin version consists of three parts:

• The CMake project version of the plugin
• The Git revision of the last commit that touched the plugin
• A dirty suffix for uncommited changes to the plugins

The VAST_REGISTER_PLUGIN macro no longer takes the plugin version in the C++ code, which may require plugins to be updated.

📝 Checklist

• All user-facing changes have changelog entries.
• The changes are reflected on docs.tenzir.com/vast, if necessary.
• The PR description contains instructions for the reviewer, if necessary.

🎯 Review Instructions

Run locally to test the dirty indicator and that rebuilds pick up changes without reconfiguration.

[tobim]

This doesn't work with the static binary build yet, because .git is not available when building with Nix. Let's talk about this tomorrow.

{
  "VAST": "2021.06.24-94-gcf69006dd9-dirty",
  "VAST Build Tree Hash": "affe98910aab0b51579bd156300f7665",
  "CAF": "0.17.6",
  "Apache Arrow": "4.0.1",
  "jemalloc": "5.2.1-0-gea6b3e973b477b8061e0076bb257dbd7f3faa756",
  "plugins": {
    "example-analyzer": "0.1",
    "pcap": "unspecified"
  }
}

[dominiklohmann]

This doesn't work with the static binary build yet, because .git is not available when building with Nix. Let's talk about this tomorrow.

We discussed this and agreed to do this in a separate PR.

This one still needs to be rebased after #1767 is merged.

[tobim]

Approving this now, but I think the example analyzer integration test needs a fix.