Hard to take back-bearings when reading hardware files

[DrongoTheDog]

Error reporting from HardwareFileReader::d3_load_validate_sections() - and presumably others - does not include (line, column) address in the file of the error, which makes it hard to find the thing. The location in the source file of each UIF token is available from UIF::Node::Src(int &, int &). And no, I don't have a reason for the source to be out of order in the .cpp file, apart from me being a prat.

[mvousden]

Here's the file, for future Mark: POETSHardware.txt