Fixes null ref exception when generating 3.0 clients with request bodies

[crfloyd]

Fixes issue where request bodies cause null ref exceptions when generating client because ActualName instead of Name should be used when creating the parameter name since this provides a fallback to 'body' in the event that Name is null.

[RicoSuter]

Thanks for the PR!

[crfloyd]

My pleasure. I didn't see any open issues for this but next, I'd like to provide support in the C# client generator for the OpenAPI 3.0 deepObject parameter for query params. What I currently need is to be able to specify a query param, 'foo' with property, 'bar' that, when set to value 'baz' in the client, will be serialized as foo[bar]='baz' in the request.

[RicoSuter]

The generators eventually need to only use the OpenAPI 3.0 properties/models (which are set by the Swagger 2.0 properties) and support additional OpenAPI 3.0 features, see #945

[RicoSuter]

Currently, OpenAPI 3.0 support is not on my priority list, as I want to first consolidate other stuff. But I'm happy to accept PRs - best would be with unit tests to avoid regressions in the future.