Mark array() method as deprecated with warning message

[hxrshxz]

Resolves #8151

Changes:

Marked both the static and instance version of the array() method as deprecated

PR Checklist

• npm run lint passes
• Inline reference is included / updated
• Unit tests are included / updated

[davepagurek]

This is currently throwing errors in the tests. Inside of classes, we don't have access to a global p5. We do have access to them in the exported addon function body though. In #8176 I dealt with something similar by patching the class in the exported addon function to give it access to these.

Also, once this does work, we probably don't want to flood the user's console with logs if they're using this a bunch every frame. We should maybe track whether or not we've logged this warning yet, and don't log it a second time.

[hxrshxz]

Thanks for your help sharing this pattern made the fix super easy

[sidwellr]

As long as this is being changed, I suggest updating the documentation as well. Change from "Returns the vector's components as an array of numbers" to something like "Returns the vector's first three components as an array of three numbers." The existing example is great; it makes clear that the result will have three numbers even for a 2D array.

I also suggest including a pointer to its replacement in the deprecation message (and perhaps something similar in the FES message):

@deprecated array() will be removed in a future version of p5.js; use the more flexible v.values instead of v.array()