[codegen] Fix camel casing of punctuated properties

[blampe]

Description

Updates node and dotnet to use cgstrings.Camel in order to correctly remove punctuation.

Fixes #15874.

Refs

• Invalid code from logging-operator crds (properties containing periods) crd2pulumi#15
• If field name contains a dash invalid Typescript is generated. crd2pulumi#25
• crd properties with - in name crd2pulumi#43
• CRD for Percona Server for MongoDB Operator generates invalid typescript: crd2pulumi#70
• Invalid NodeJS Identifiers Generated crd2pulumi#76
• [nodejs] Generated code is broken for grafana crd crd2pulumi#92
• Invalid typescript code generated when crd property is hyphenated/pascal case (-) e.g auto-scaler crd2pulumi#101
• Invalid typescript code produced when generating for strimzi crds  crd2pulumi#103

Checklist

• I have run make tidy to update any new dependencies
• I have run make lint to verify my code passes the lint check
  • I have formatted my code using gofumpt

• I have added tests that prove my fix is effective or that my feature works

• I have run make changelog and committed the changelog/pending/<file> documenting my change

• Yes, there are changes in this PR that warrants bumping the Pulumi Cloud API version

[pulumi-bot]

Changelog

[uncommitted] (2024-05-30)

Bug Fixes

• [sdkgen/{nodejs},{dotnet}] Fix camel casing of punctuated properties
  #16197

[Frassle]

This isn't a valid C# identifier.

[Frassle]

This isn't a valid TS identifier

[Frassle]

I'm not confident this is actually correct. I don't see annotations being emitted to tell the SDK to serialise/deserialise to the wire protocol with the hyphenated names.

There's also a bit of me that is not really keen on saying we support names like this in schema. I'd rather that the thing building the schema is responsible for coming up with "identifier like" names (e.g. fooBar, not foo-bar) rather than trying to make codegen deal with any possible string.

See https://docs.google.com/document/d/1ns07htpLjw0dJPn5p7TBPVULvwwYc1Pl7l1c1jdGXoY/edit#heading=h.cpxu86q7zc1s for some discussion we've had around property/type naming systems in the past.

This probably needs bringing to iac ideation meeting to be discussed.