Add support bazel builds

[jayakasadev]

There's been a few attempts at supporting bazel for DPDK in the past. Many were abandoned due to the work required to maintain the projects. This PR tries to do it in as minimal a way as possible.

Maintenance:

• BUILD.bazel will require the most maintenance in the future because it explicitly specifies the build outputs. So any changes will need to be reflected here.
• If meson requires newer or more python deps, then they will need to be added to bazel/requirements.in and bazel/requirements.txt will need to be updated by running bazel run //bazel:requirements.update

Beyond that, bazel is using meson to build the target. So core devs shouldn't need to worry about making changes specifically for bazel.

Major changes:

• Moved buildtools/coff.py into buildtools/pmdinfogen.py because bazel does not allow relative imports.
• modified config/meson.buildand lib/meson.build to allow users to use non-system numactl
  • this allows the bazel builds to be more hermetic.

Expected usage pattern for bazel users:
In MODULE.bazel add the following:

bazel_dep(name = "dpdk", version = "")

git_override(
    module_name = "dpdk",
    commit = "<SPECIFIC COMMIT>",  
    remote = "https://github.com/DPDK/dpdk",
)