ClientMethodTemplate: Remove method parameters that can be obtained from other parameters and Improve ClientType to WireType function

[anuchandy]

1. In ClientMethodTemplate (and its extended types) methods, there is no need to pass ProxyMethod as an explicit argument, since it can be obtained from ClientMethod argument.
2. Similarly, no need to provide List<ProxyMethodParameter> explicitly when it can be obtained from ClientMethod ::ProxyMethod::parameters
3. The function convertClientTypesToWireTypes has been simplified and updated to be extensible for future prs that aim to simplify inherited templates such as client core.
4. Few other minor cleanup for readability.

AutoRest validation pr.

[github-actions]

No changes needing a change description found.

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension

[haolingdong-msft]

The changes look good to me.
Good to see we have autorest validation pipeline now. Would like to learn more about working with autorest core submodule(we had submodule before I leave, but at that time, we will just sync the code from typespec repo to autorest.java's core module in local before doing release). Got below questions:

• My understanding is this pipeline is to run the tests (e.g. vanilla test, fluent test, typespec test) and make sure those are not broken by this pr's change. But I saw it is triggerred on main branch in autorest.java, so it does not include this pr's change, I'm a bit confused on what is this pipeline validating?
• Is the pipeline triggered manually and when do we trigger it?
• What is the current process of updating codegen?

[XiaofeiCao]

Hi @haolingdong-msft , from my understanding:

• My understanding is this pipeline is to run the tests (e.g. vanilla test, fluent test, typespec test) and make sure those are not broken by this pr's change. But I saw it is triggerred on main branch in autorest.java, so it does not include this pr's change, I'm a bit confused on what is this pipeline validating?

There is a submodule commitId to set core to the latest commit ID of your PR's branch. This is equivalent to checking-out the branch under core when doing autorest.java PR.

• Is the pipeline triggered manually and when do we trigger it?

Currently we trigger it manually. For validation on Swagger part, it's more convenient than preparing a PR in autorest.java repository.

• What is the current process of updating codegen?

I believe this part hasn't been changed.

Weidong and Anu may provide more context on this.

[weidongxu-microsoft]

To Haoling, the verification pipeline is mostly for convenience. It takes a commitId or a branch.

For PR that we do need a new release, or need version bump on dependencies, or sync of tests, one probably would just go there and create a PR on autorest.java

But for task like refactor, that pipeline could be a help.