`bpf_printk` provider GUID and verbosity changes.

**Issue:**

Currently bpf_printk uses eBPF tracelogging provider and the trace level is hard coded to INFO. This does not provide enough flexibility to the BPF program authors who want to use bpf_printk in their BPF programs but do not want it to be at INFO level, as it floods eBPF traces.

**Proposals**
There are a few options for this:
1. Use a new provider different than used for eBPF for bpf_printk.
2. Allow each BPF program author to choose their own provider GUID. BPF2C can be enhanced to take provider GUID as an optional input.

Orthogonal to the above options:
Add a new Windows only helper function `bpf_printk_dbg`. This will emit traces at VERBOSE level. Note that this can be implemented in conjunction with option 1 /option 2 above.