refactor!: Make TextElement more usable on its own

[luanpotter]

Description

This is part of my ongoing effort to simplify the text rendering pipeline.
My ultimate goal is to:

• get rid of renders
• rename formatters to renderers
• make the interface complies to both
  All details are specified here: refactor!: Simplify text rendering pipeline #2663

As a first step to break down that huge PR, this makes a small change to TextElements to make them more useful

This PR will:

rename render -> draw

draw becomes the "internal", underlying impl, raw method, that just draws the element w/ any custom options

add a new render method that takes in more options

this does not need to be extended by every impl.
this is for end users and accepts parameters like position and anchor to be more in line with the renderer interface

Checklist

• I have followed the Contributor Guide when preparing my PR.
• I have updated/added tests for ALL new/updated/fixed functionality.
• I have updated/added relevant documentation in docs and added dartdoc comments with ///.
• I have updated/added relevant examples in examples or docs.

Breaking Change?

• Yes, this PR is a breaking change.
• No, this PR is not a breaking change.

Migration instructions

This is technically a breaking change but should have no effect for users, unless you are creating your own custom TextElements. In that case, to migrate:

• rename your render method to draw

[spydon]

Lgtm!