Attempts to clear up a common misconception about the functionality of
the `denylist` key.

Yara publicly exposes the definition of various str functions like
strlcpy, strlcat and so on if they are not present on the system
it is compiled on.

This is not ideal because other libraries use custom implementations
of those functions and those symbols would collide with
the public ones from yara, therefore we rename them
to avoid the collision.

This speeds up the configuration phase and simplifies having
control of the compilation flags used.

Additional changes were required due to other libraries incorrectly
depending on glog and gflags cmake code or headers.
smartmontools especially, was incorrectly publicly depending
on its own config.h, which was though taken from glog
when smartmontools libsmartclt.h header was included by user code.
A fix has been done on the smartmontools side and so the submodule
commit we refer to has been updated.

The status badge was incorrectly specified and it was "merged"
with the Azure one.

Add a link that sends to the Github Actions builds on the master branch
when the status badge is clicked.

The upstream repository was failing to do shallow clones.

osquery was already linking with -pthread and so linking
to libpthread on Linux, but it wasn't always defining
the _REENTRANT macro which is done by the -pthread option
given at compile time.
Although in the third party libraries that need it,
it should've been defined in other ways (directly or via a config.h),
always add -pthread for correctness and consistency.

Note: macOS doesn't need -pthread at link time because
pthreads are already implemented inside the libc library.

This is a follow-up to #6893 fixing an additional cross-platform
compatibility issue with the relative path check in Yara.

Make the relative filepath check cross-platform.

Fixes #6788

This table provides output similar to "docker history" command.
See: https://docs.docker.com/engine/reference/commandline/history/
created_by column has useful information related to the command history

libdpkg is leaking memory on every initialization.
Initialization happens everytime deb_packages gets queried.

The memory leaked is allocated for the "triggersdir"
global variable by "dpkg_db_get_path" called in "trigdef_update_start".
"trigdef_update_start" is called by "trig_incorporate" just after
the memory for "triggersdir" has been allocated.
In some occasions "trigdef_update_start" is also called two times in a
row. In all these cases the memory do not get deallocated in between calls,
so the old memory is lost.

Since the result of "dpkg_db_get_path" depends on the database dir that
has been set, and in the "trigdef_update_start" function it's not possible
to know if it has changed from the previous allocation or not,
it's necessary to always deallocate vs just avoid to call "dpkg_db_get_path".

Fix also a couple of other leaks on error.

- Downcasting a shared_ptr to a type T2 that's not a derived class or a base class of T1,
  even if they share the same base class B, it's undefined behaviour.
  For instance BPFEventPublisher inherits from EventPublisher<BPFEventSC,BPFEventEC>,
  which is a template that inherits from EventPublisherPlugin, which
  further inherits from Plugin.
  The register function was called passing an instance of std::shared_ptr<BPFEventPublisher>
  which was implicitly upcasted to std::shared_ptr<Plugin> as the
  function parameter.
  Then such parameter was downcasted to std::shared_ptr<EventPublisherPlugin>
  (which was fine), then further downcasted to std::shared_ptr<BaseEventPlugin>
  which actually was std::shared_ptr<EventPublisher<SubscriptionContext, EventContext>>.
  Although the two EventPublisher template parameters are base classes
  of BPFEventSC and BPFEventEC, the resulting concrete EventPublisher
  class is not related to BPFEventPublisher, so this is UB.
  This was done in an attempt to have a common type for all publishers
  to be used to store them into a std::map. Instead of using such type,
  use EventPublisherPlugin.
  A very similar thing happens with subcribers.

- Fix an incorrect success when a std::shared_ptr<Plugin>
  fails to be downcasted to a std::shared_ptr<EventPublisherPlugin>,
  in EventFactory::registerEventPublisher.

- Substitute dangerous reinterpret_cast on a pointer to a member function
  callback in EventSubscriber<PUB>::subscribe with a safer approach
  which uses a lambda that captures the object it has to call the callback on
  and properly converts the arguments, downcasting them to the appropriate type.
  Also remove a redundant template parameter.

- Add a virtual destructor to SubscriptionContext and EventContext
  structs since they are inherited from
  and used in a polymorphic context as pointers.

Do not take a reference to a shared_ptr to be accessed
after being removed from the last persistent place
that was possibly keeping it alive.