Fix: tracepoint instrumentation constructor order issue

If the linker decides to run a constructor from a tracepoint probe
before the constructor from the application, a recent modification
(commit 558b9d86247004f8e9bbaf8c982f3b2b182093d1) allowed that the wrong
constructor execution order could prohibit the program's tracepoints
from being registered.

Fix this by making two separate constructors.

Fixes #487

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Version 2.2.0-rc1

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Remove redondant "hello" test and move "hello-static-lib" to doc/examples

The examples are now automatically built as part of the default make target.

The "hello" test verifies that an application with statically embedded
tracepoint providers can build. This is covered by "easy-ust" in
doc/examples since we now build the examples.

Move the "hello-static-lib" test to doc/examples.

This should provide a complete and easy to understand examples to users who
wish to integrate tracepoint providers to their applications

Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>