Particle command using vanilla particles causing molang errors in content log

Partner Rank: 2

Partner Team Reporting: Nitric Concepts

Verification Build: 1.14.30 release build 3692779
Regression Build: "As far as I'm concerned, there isn't a regression build where this worked.  It was believed in the community that this is hard coded.  Someone other partner was having this issue with some vanilla particles being used as well, and it was believed to be some vanilla particles that's intended to be used with hard coded parameters."

Summary:
Executing a command to use vanilla particles cause molang errors on startup.
Impact: Release, Time, Development.

Repro Steps:
Step 1: Have a item renamed with custom color codes, example would be renaming coal to "§bPresent" using lang files.
Step 2: Have a function file with the command "execute @e[type=item, name="§bPresent"] ~ ~ ~ particle minecraft:balloon_gas_particle ~ ~0.75 ~"
Step 3: Place a command block on repeating & always running, and input the aforementioned function within it.
Step 4: Attach the world with the behavior pack and resource pack containing the aforementioned files. Export the world as a template.
Step 5: Run the template and the errors should pop up on start up.

An example of this bug can be obtained from a recent submission as discussed in the nitric concepts slack channel.

Repro Rate: 3/3

Observed Results:
```
[Molang][error]-Error: accessing a variable that doesn't exist: variable.direction.x
[Molang][error]-Error: accessing a variable that doesn't exist: variable.direction.y
[Molang][error]-Error: accessing a variable that doesn't exist: variable.direction.z
```
Errors appear on start up.

Expected Results: No error on startup.

Screenshots / Videos Attached:

Notes: We've used a vanilla particle minecraft:egg_destroy_emitter and it didn't have errors on start up.