Curly (smart) quotes don't work on command arguments

When using /commands, one may use "quotes" to surround an argument containing spaces to get it to be treated as a single string.

However, this does not work when using “curly quotes”. The curly quotes are interpreted as literal characters instead of quotation marks.

Tests to reproduce

• /effect @p "l o l" 5 . Note that the syntax error points to »l o l«
• /effect @p “l o l” 5 . Note that the syntax error points to »“l«