make venv input optional

[derekk-nm]

the venv input assigned to some actions has not been set in a variety of workflows, in spite of it being required.
In fact, the actions already have code to check the value and provide a reasonable substitute for it if it wasn't provided.
I've;

• modified the input declaration to indicate that it is optional,
• with a default empty string value, and
• removed the references to it from workflows that were passing in blank values.

I also updated the nm-lm-eval action to use the same pattern to test the value of the venv input, so that it is consistent with the other actions.

This nm remote push run demonstrates that at least the nm-test workflow and called actions continues to work as expected.

[andy-neuma]

changes look okay, but wondering if we should just remove it entirely. we don't really use it anymore.

[derekk-nm]

@andy-neuma , just to confirm, you're saying that we don't really need to be using virtual environments in these actions? So I can just remove the if block altogether, right?
Or are you saying that we should always just use a virtual env constructed with the COMMIT id? pull the content of the if block into the same level as the rest of the shell command?

[andy-neuma]

@derekk-nm - i'm suggesting we just remove the venv usage. you can just delete the "if" block.

[andy-neuma]

thanks

[derekk-nm]

Thanks @andy-neuma, I had a patch ready that deleted the if blocks, so I've pushed here. will wait for the checks to complete.

[derekk-nm]

moving to nm-vllm-ent