[fix] Test more package names converted to CamelCase in 'conan new -t' command

[jgsogo]

Changelog: Bugfix: Variable package_name in conan new -t <template> command contains a CamelCase version of the name of the package.
Docs: conan-io/docs#1663

[SSE4]

what's the reason to convert package names to CamelCase? it's known to cause troubles on case-insensitive file system, and I thought we agreed to use only lower-case for package names.

[memsharded]

what's the reason to convert package names to CamelCase? it's known to cause troubles on case-insensitive file system, and I thought we agreed to use only lower-case for package names.

It is just the name of the class in the conanfile.py, not the package-name. The naming of variables is confusing.

But to be honest, I don't fully got why this PR is necessary, what is fixing, as the class name is mostly irrelevant?

[jgsogo]

I was having a look at the conan new command as another good candidate to take advantage of the templates approach, reading the docs, having a look to the sources,... and I found this package_name name variable (really bad name, yes, but documented 🤷 ).

The docs say it is converting the actual package name to camel case (to be used for the classname), but with the existing regex it was not working for some package names:

• "my-package" -> "Mypackage"
• "my.package" -> "Mypackage"
• "my+package" -> "Mypackage"

Now it is returning "MyPackage" for all of them

[memsharded]

Yep, really bad, bad name...