Updated from latest NI-DCPower exports

[reckenro]

What does this Pull Request accomplish?

• Updates NI-DCPower metadata/proto to come from hapigen export: nidcpower_grpc_device 23.0.0d114
• Updates NI-DCPower header from hapigen export: nidcpower 23.0.0d114
• Updates NI-DCPower nidcpower.lib from nidcpower 23.0.0d114

Breaking changes

• Correction for wrong input on ErrorQuery: updated so ErrorQueryRequest doesn't have error_message field but instead the ErrorQueryResponse has it
• ExportAttributeConfigurationBuffer and ImportAttributeConfigurationBuffer configuration fields updated from repeated fixed64 to bytes. This correction matches the header files and matches the similar function signatures in nidmm.proto and niscope.proto.

Why should this Pull Request be merged?

Covers the NI-DCPower part of the following task:

AB#2172471 : Import 23.0.x hapigen exports into grpc-device (nidcpower, niscope)

What testing has been done?

Built locally and NI-DCPower system tests still pass.

[dmondrik]

@reckenro once your ni-central PR goes in, I'll pull together all the latest exports (dcpower and scope) and put them into an official PR for this.

[reckenro]

@astarche / @dmondrik , for the header and the metadata/proto I imported from 23.0.0d92 (latest export). But when doing the same for the nidcpower.lib file, I was getting linking errors for about six nidcpower_... methods.

Those methods line up with some recent changes that went into DC Power in hapigen which will be resolved with this AzDo bug. So I took the most recent export whose nidcpower.lib worked with the other changes in this PR. That happened to be nidcpower 23.0.0d83 which matches what I suspected because it is the export right before the problematic change went in (see ni-central commit)

All that being said, is it okay to include an older nidcpower.lib file or should we wait for that Bug to be fixed and get a new nidcpower.lib from a future export?

[dmondrik]

All that being said, is it okay to include an older nidcpower.lib file or should we wait for that Bug to be fixed and get a new nidcpower.lib from a future export?

If an older import .lib file allows it to build correctly, then I think it's fine to proceed that way. There's no reason to block this arbitrarily.

[reckenro]

Windows system tests are currently busted because of issues with the grpcbot we run the tests on. It will be stuck in the queue forever. They pass locally and also run on Ubuntu as part of the run_ubuntu_system_tests step and passed there. So I'm going to cancel the run_win_system_tests step and submit.