Allow characters other than [A-z] to be used in class diagrams

[aliyome]

Is your feature request related to a problem? Please describe.

In the class diagram, I tried to put the field and method names in Japanese but I couldn't do it.
For Japanese, the use of Japanese in class diagrams is very descriptive and valuable.
In the current specification, field and method names are specified as \w+ in regular expressions, so only [A-z] can be set.

Describe the solution you'd like

I want to change the regular expression to .+, and I want to allow characters other than [A-z].

Describe alternatives you've considered
None

Additional context
Please see the following figure for the current behavior.
If the field and method names are specified in [A-z], they work correctly.
However, if the field name and method name are specified with characters other than [A-z], such as Japanese, part of the method name will be missing, "*" and "$" will not work, and the return type will not be drawn.

If this is unexpected behavior, would it have been better to create an issue as a bug report?

[aliyome]

Specifically, I would like to modify this as follows.
However, only this fix causes some tests to fail, so we need additional mods.

mermaid/src/diagrams/class/svgDraw.js

Lines 285 to 286 in 2524dfd

	const fieldRegEx = /^(\+|-|~|#)?(\w+)(~\w+~|\[\])?\s+(\w+) *(\*|\$)?$/;
	const methodRegEx = /^([+|\-|~|#])?(\w+) *\( *(.*)\) *(\*|\$)? *(\w*[~|[\]]*\s*\w*~?)$/;

-  const fieldRegEx = /^(\+|-|~|#)?(\w+)(~\w+~|\[\])?\s+(\w+) *(\*|\$)?$/;
-  const methodRegEx = /^([+|\-|~|#])?(\w+) *\( *(.*)\) *(\*|\$)? *(\w*[~|[\]]*\s*\w*~?)$/;
+  const fieldRegEx = /^(\+|-|~|#)?([^~]+)(~[^~]+~|\[\])?\s+([^!~$]+) *(\*|\$)?$/;
+  const methodRegEx = /^([+|\-|~|#])?(.+) *\( *(.*)\) *(\*|\$)? *(.*[~|[\]]*\s*.*~?)$/;

[jgreywolf]

We are no longer using the fieldRegEx and methodRegEx in order to determine how to organize members. After the release of #4534 this issue may be resolved

[aliyome]

Thank you for your support. I apologize for my delayed response. I have checked the current release and confirmed that the issue has been resolved. Thank you!!