[Feature Request] Support defining memory type in custom op's I/O

### Describe the feature request

Custom ops may have inputs/outputs on different memory locations. Internally we can specify inputs/outputs memory type by calling KernelDefBuilder__InputMemoryType() or KernelDefBuilder__OutputMemoryType when registering kernels. It would be nice if this can be supported in custom op. The aim is to mitigate memory copy between device and host.

### Describe scenario use case

custom beam search op

Start by tracing custom-op registration and the existing KernelDefBuilder__InputMemoryType() and KernelDefBuilder__OutputMemoryType APIs named in the issue. No file or test is identified, so first locate the custom-op kernel definition path and related memory-copy tests; done means custom ops can declare input and output memory types and the beam-search scenario avoids unnecessary host-device copies.

Written by the indexing model from the issue text.