Bug/1478 er diagram unicode support

[Mikek16]

📑 Summary

Resolves #1478

📏 Design Decisions

add literal unicode character range to ALPHANUM regex

[netlify]

✅ Deploy Preview for mermaid-js ready!

Name	Link
🔨 Latest commit	a656550
🔍 Latest deploy log	https://app.netlify.com/sites/mermaid-js/deploys/657b4270eff48e00085de7df
😎 Deploy Preview	https://deploy-preview-5146--mermaid-js.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

Merging #5146 (a656550) into develop (6e64556) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #5146   +/-   ##
========================================
  Coverage    79.37%   79.37%           
========================================
  Files          166      166           
  Lines        13878    13878           
  Branches       705      705           
========================================
  Hits         11016    11016           
  Misses        2710     2710           
  Partials       152      152           

Flag	Coverage Δ
e2e	85.18% <ø> (ø)
unit	43.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[sidharthv96]

What we normally do to support unicode is quoted strings, like below.

mermaid/packages/mermaid/src/diagrams/pie/parser/pie.jison

Lines 30 to 33 in 52bb31b

	["] { this.begin("string"); }
	<string>["] { this.popState(); }
	<string>[^"]* { return "txt"; }
	"pie" return 'PIE';

I'm not sure of the implications of the suggested approach of adding the unicode character range. @nirname @aloisklink any potential issues?

[aloisklink]

After having a look at the JISON file for ER Diagrams, I believe every field that uses 'ALPHANUM' already supports 'ENTITY_NAME' (which is confusingly named), which does support unicode characters, as long as they're quoted, e.g.

```mermaid
erDiagram
    "🌋" ||--o{ "Hiking Trail 🥾" : "contains 🧭"
    "🌋" {
        string name "name: 名"
        float height "my 📈"
        string sector
    }
```

renders as

erDiagram
    "🌋" ||--o{ "Hiking Trail 🥾" : "contains 🧭"
    "🌋" {
        string name "name: 名"
        float height "my 📈"
        string sector
    }

Loading

Therefore, this change isn't needed. However, the documentation for this is missing, if you want to add it @Mikek16.

Both attribute types and attribute names don't support unicode.

It would be nice if we could somehow also throw a nicer error message when somebody tries to use unicode characters and they're not using the "" syntax, but I don't know if jison has support for that.

[nirname]

ENTITY_NAME should be enough, but I don't have any objections about extending ALPHANUM in this case. We have to ensure that EOF is not in that unicode range.

But as @aloisklink suggested, I would rather have documentation updated first, and the see how many people still encounter this problem

[nirname]

@Mikek16 gentle remidner, just want to know if there is any further work expected on this?