Because Pixi init is async, we need to keep track of that promise, and delay
many things until after it has settled.

- commented out linebuilder for now
- commented out dashed lines for now
- a few changes in `drawShape()` -> `poly()`
- new constructor for `PIXI.Geometry({options})`
- pin version to v8.3.3
- move `@esbuild/darwin-arm64` to optionalDependencies
- still thinking about how to get texture atlases working

…xi js now

… raw string specifiers.

…nd maskSource now has a context, not a geometry.

…out using resource.load(), which no longer exists.

…data to obtain and allocate in the texture atlas. Bitmap text seems to work!

…m being added to parent containers.

…local bounds returned by the sprite.

…'something'.

…), lines now appear

…le changed to circle, name changed to label, drawRect changed to rect, drawPolygon changed to poly

…traces.

…orrecting the fill input.

…called after the geometry-creating methods.

…ach allocated texture.

…background tiles.

Note that we do not need the submodules anymore
(maybe we did not before either)
`@pixi/util`, `@pixi/display`, `@pixi/graphics`, etc
These things are all bundled in `pixijs`

`@pixi/settings` is removed in v8

This is stuff like
- drawCircle -> circle
- drawRectangle -> rect
- drawPolygon -> poly

Also, be more consistent in how we import the Pixi objects,
prefer just using the star import everywhere:
`import * as PIXI from 'pixi.js';`

This was unnecessary, the AtlasAllocator can continue to deal with
whatever texture sources inputs we send it.

It won't work because:
    "@rapideditor/pixi-dashed-line": "file:../pixi-dashed-line",
    "@rapideditor/pixi-texture-allocator": "file:../pixi-texture-allocator",

- Added several render options at init that might be helping
- Commented out the `graphicToTexture code`
- Several renames from `getChildByName` -> `getChildByLabel`

Also, be more consistent in how we import the Pixi objects,
prefer just using the star import everywhere:
 `import * as PIXI from 'pixi.js';`

The variables are a little different in v8.
This is still hacky, but I'm not sure another way around it.

The `TickerPlugin` code that adds the Ticker to `PIXI.Application`
really wants to do `ticker.add(this.render, this, UPDATE_PRIORITY.LOW);`
even if we were to replace it with a different Ticker.

Our issue is we need to call `render` ourselves at the time of our choosing.

Our texture atlases seem to be getting corrupted.  This will show up as either
the Bitmap Fonts getting messed up, or leaking into the background tiles.

I've tried commenting out the minimap for now, and also doing some other
cleanups around the code to isolate whether textures are getting destroyed
propertly.

This switches from using `@rapideditor/pixi-texture-allocator`
"fork of the plugin" to just including the code we need in Rapid.

The old code worked ok for v7, but the v8 upgrade was causing texture
corruption, and it became easier to just massively simplify things
than to debug and fix whatever was going on with the plugin code.

Also passing more options in the AtlasSource/TextureSource constructor,
preferring to leave nothing to chance here.

Also add some more comments and make sure everything has labels for
better debug-ability.

This is an older trick that I removed in dd24e91
In pixi v7, we switched to using `SVGResource`, which did this for us
In pixi v8, `SVGResource` is gone and there is now a SVG parser, but it
 doesn't fully support svg syntax, so we can go back to the old way for now.

- Uncomments the `PixiLayerLabels` layer
- Restores both bitmap text (ascii text placed next to pins)
  and textured text (complex text next to pins or along ropes)
- Moves the text-to-texture code from `PixiLayerLabels.getLabelSprite()`
  to `PixiTextures.textToTexture()` in the texture manager
  (there are other functions in texture manager like this)

Todo:
- Polygon labels remain commented out because we need to calculate
  the buffer inside the perimeter.  We were (ab)using `PIXI.buildLine`
  for this, but maybe there is a better way now..

Also:
- There was previously some code in `PixiLayerLabels` that would do
  `toGlobal(position, point, true)` to skip updating the transform
  We can not pass `true` for `skipUpdate` anymore in pixi v8,
  Probably related to pixijs/pixijs#10433

This was used before for calculating buffers around lines,
which was used for hit testing and label placement.

…i has started, and change the allocator to send ImageBitmaps instead of raw pixel arrays.

I went back to doing things the old way:
- Make a `PIXI.Graphic` using strokes,
  Then force generate it’s geometry,
  Then and extract the geometry into a `PIXI.Mesh`.

The mesh works well for both hit testing and masking.

Other approaches that didn't work:
- In Pixi v8, stroke graphics can work for hit testing, but the
  hit test ignores `alignment` which we need when partial filling.

- Tried using our `lineToPoly` buffer generating function
  to convert the stroke into a Graphic that would both hit test and mask,
  but it's too buggy. (it uses pixi's linebuilder, then walks the perimeter)