fix: manual cleanup capability of text and memory #7700

[uppathidev]

Resolves #7700

Changes: FIX: manual cleanup capability of text and memory

Screenshots of the change:

PR Checklist

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

[welcome]

🎉 Thanks for opening this pull request! Please check out our contributing guidelines if you haven't already. And be sure to add yourself to the list of contributors on the readme page!

[davepagurek]

Hi @uppathidev! Currently we're only adding new features to p5 2.x, which is in the dev-2.0 branch. Do you think you could base your changes off of that branch and create a PR into it instead?

[davepagurek]

I think we can just make this method directly in the texture class in this file rather than adding it to the prototype here.

[davepagurek]

Also, some general thoughts:

• I think we maybe don't want to add methods directly onto things like a p5.Image, as they can actually be used on multiple renderers, and their textures will exist separately on each renderer. Instead, we likely want a method on p5.RendererGL that you call on a visual, like freeTexture(myImg) (similar to how freeGeometry works for p5.Geometry.)
• When we remove text textures, this is currently what we do:

  p5.js/src/webgl/text.js

  Lines 809 to 813 in 3eae276

  	const tex = this.textures.get(data);
  	if (tex) {
  	tex.remove();
  	this.textures.delete(data);
  	}

  This is probably all we need inside of a freeTexture method.