Add test network agent for ncproxy dev work

[katiewasnothere]

This PR contains a test version of a vnetagent that we can use locally when doing dev work with ncproxy. This is not meant to be used outside of a testing environment.

This PR additionally updates cmd/ncproxy/nodenetsvc/nodenetsvc.proto to match the current version being used by the AzNet team.

Signed-off-by: Kathryn Baldauf kabaldau@microsoft.com

[katiewasnothere]

@dcantah in particular :)

[kevpar]

One note: I would probably put this under internal/tools since it's a test binary.

[dcantah]

Thanks for making this btw ❤️ I'll keep the review up on Monday

[dcantah]

I'm wondering how we could make some useful tests here.. We need to launch ncproxy and the test agent and make calls between them to have anything of value

[katiewasnothere]

I'm wondering how we could make some useful tests here.. We need to launch ncproxy and the test agent and make calls between them to have anything of value

@dcantah I was planning for this to mostly be useful for devs when manually testing. I'm still trying to figure out how we should write tests for ncproxy.

[dcantah]

LGTM! Don't think we need to hold off on this for much, think you'd rather have it in already. Misc. cleanup, some better signal handling, and some os.Exit removals that I'd like to see, but the rest looks fine (just push new commit and squash on check in and we're all good). Had a small q on an a new nns call that's added here also that I'd like an answer on.

[dcantah]

re-lgtm