Add ni-apis as submodule and regenerate discovery client LabVIEW code

[pakdev]

• This contribution adheres to CONTRIBUTING.md. (Required)
• Automatically post PR comments with images for G code changes? (Recommended for small changes)

What does this Pull Request accomplish?

The discovery_service.proto in the ni-apis repo is more updated than the one here. For an upcoming change, I wanted the ServiceDescriptor.versions property. Thus, I added ni-apis/protobuf as submodules and regenerated the LabVIEW gRPC bindings from the new proto files.

Why should this Pull Request be merged?

Because our proto files should stay up-to-date and our discovery client LabVIEW code is now up-to-date.

What testing has been done?

Ran run_tests.vi

[dixonjoel]

I'm not super fluent with submodules, but I think everything under the ni-apis folder comes directly from that repo and is showing because you're adding the submodule? So I think we don't need to review anything under there?

[dixonjoel]

@pakdev Waiting to approve until the checks all pass.

[bkeryan]

I'm not super fluent with submodules, but I think everything under the ni-apis folder comes directly from that repo and is showing because you're adding the submodule? So I think we don't need to review anything under there?

That looks wrong. When you added ni-apis as a submodule to measurement-plugin-python, GitHub displayed the submodule as a link and didn't display all of the files inside.

[pakdev]

I'm not super fluent with submodules, but I think everything under the ni-apis folder comes directly from that repo and is showing because you're adding the submodule? So I think we don't need to review anything under there?

Right

[pakdev]

On second look, it appears I shouldn't have pushed the contents. I'll fix that

[pakdev]

Not sure what's going on with these tests - might need some help tomorrow morning. Not able to reproduce these 1003 errors in my branch...

[pakdev]

@pakdev Waiting to approve until the checks all pass.

Passing now