This is in preparation for making a unified interface for dpu tools that
is able to detected the hardware its running on an call its respective
tools

ipu: Remove IPU dir

Remove redundant fwversion

Remove redundant fwup

Remove redundant fwdefaults

Remove listbf script

The list bf script has been integrated into the list dpus command and
function. Now we can use this information to auto detect hardware and
have the tool behave accordingly depending on its hardware

Make the imports match the new structure

Many of these functions aren't necessarily tied to the ipu so moving it
to the common module makes more sense

Matching imports to new structure

Since we want to unify the scripts behind dpu-tools we should also build
the tools using the same Dockerfile

This enum keeps us with a structured way to track different DPU types.
Previously we would just use hardcoded strings, but with this class we
can even validate if the DPU Type is within our tracked types

Since DPU tools often relies passing the args to each function, it would
be nice to have a data structure to bundle all of this in. Likewise it
would be good if we could also keep track of what DPU type are working
with.

This script is useful because it lets rshim run in the background, which
the Bluefields DPUs need to console into them.

…s well

By making this class we can keep together related logic to reset,
upgrade and version firmware across dpu types

Many of the Bluefield scripts requires capturing the output. It would be
better to have it default to capturing output and have an option to turn
it off when we think its not useful

Here we are using a single mode subcommand that can be used to retrieve
the mode and set if passed the set-mode flag

…dule

…ll BF reset