Arm backend: Add WhyNoPartitionReporter and report rejected nodes (#8963)

With more complex checks for if nodes are supported or not, it can
probably be complicated for a user to understand why a ceratin node was
rejected from partitioning.
The WhyNoPartitionReporter attempts to mitigate this by producing a
table with all rejected nodes with a reason for why they were rejected.

The reasoning behind using a class rather than log statements is
- The table keeps all reject information in the same place.
- Uniform formatting.
- Only log the first reject report of a node.
- Easier to change how and when the output is logged/dumped to file.

Signed-off-by: Erik Lundell <erik.lundell@arm.com>