Historically, capstone varies in requiring either <capstone.h>
or <capstone/capstone.h> include depending on version and the
way how it has been installed. This has already been an issue
before, and will likely become an issue again with capstone
5.0 which seem to have changed this aspect once again.
Recognize both ways in the meson check, but prefer <capstone.h>
so it's easy to override which capstone to use by
pkgconfig's --cflags (or --extra-cflags).
Signed-off-by: Michael Tokarev<mjt@tls.msk.ru>
---
v2: use cc.has_header, not cc.compile (pm215)