Remove configure script

[lava]

📔 Description

To quote the corresponding story, the main reasons for removing:

• The script is called configure but does not act like a standard configure script, leading to confusion for people who just want to plug the build into some automated system with hooks. We usually have to tell them "please just ignore the configure script, we are actually using cmake as build system, yes we know its confusing".
  • It does not operate in the current directory by default
  • It overwrites the contents of any existing directory named build/ by default
  • It does not understand all the same default options that autotools-generated configure scripts have
• Its easy to forget to add new features to the configure script, leading to a divergence over time
• It slows down development since we have to invest time in updating it every time we touch the build system.

📝 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

[dominiklohmann]

Love to see this done so much that I am commenting this on my day off. 🎉

[JoeLoser]

I like this. Is there any plans to remove scripts use of configure? E.g. https://github.com/tenzir/vast/blob/a2cb4be879a13cef855da2c1d73083204aed4dff/scripts/clang-build-analyzer#L37 and perhaps others.

[lava]

@JoeLoser Absolutely, I used git grep to search for any occurences in the scripts but I must have missed this one.