Support DisposableNamedOnnxValue inputs in c# Run()

[hariharans29]

Description: DisposableNamedOnnxValue inputs in c# Run() inputs are to be supported as ``DisposableNamedOnnxValueisNamedOnnxValue`.

This change has the following parts:

1. Add logic to handle DisposableNamedOnnxValue inputs to Session Run()
2. Support a setter for the names of NamedOnnxValue/DisposableNamedOnnxValue. This is required if someone were to pass in the output of Run() to the input of another Run() as the names of the input feed is likely to be different from the name of the output feed.
3. Tests

Motivation and Context
Resolve #2983

[hariharans29]

Synced offline with @fs-eire. After discussing, we felt DisposableNamedOnnxValue inputs in Run() should be accommodated as DisposableNamedOnnxValue is NamedOnnxValue (it is a derived class). Adjusted the PR contents accordingly.

[fs-eire]

as discussed offline with @hariharans29 , NamedOnnxValue should be kept stateless. it does not implement interface IDisposable so it should not hold the IntPtr inside. ToNativeOnnxValue may need to be updated so that it outputs a boolean value to help Run() to determine whether to clean up the value or not.

for adding a setter to Name, this is a valid requirement for users to pass the output as input to another inference session. There are 2 options to support this :

• enabling users to change the Name property of a NamedOnnxValue object
• enabling users to create a new NamedOnnxValue object by performing a shallow copy from another.

it looks like both options have pros and cons so I would like to hear from more people - @jignparm @pranavsharma

[hariharans29]

ctor is private now as per @fs-eire 's suggestion

[hariharans29]

as discussed offline with @hariharans29 , NamedOnnxValue should be kept stateless. it does not implement interface IDisposable so it should not hold the IntPtr inside. ToNativeOnnxValue may need to be updated so that it outputs a boolean value to help Run() to determine whether to clean up the value or not.

for adding a setter to Name, this is a valid requirement for users to pass the output as input to another inference session. There are 2 options to support this :

• enabling users to change the Name property of a NamedOnnxValue object
• enabling users to create a new NamedOnnxValue object by performing a shallow copy from another.

it looks like both options have pros and cons so I would like to hear from more people - @jignparm @pranavsharma

Made the change to keep NamedOnnxValue stateless as it was previously.

[yuslepukhin]

This instance of DisposableNamedOnnxValue has already been disposed [](start = 37, length = 67)

Should be a bug?

[hariharans29]

bug in the user code ? Probably. But they get a user friendly error message this way...

[fs-eire]

[jignparm]

LGTM.