Implement mvp party actor

[krbz999]

• Adds party actor.
• Deprecates canvas.tokens.performTokenPlacement in favor of canvas.tokens.placeToken to be in line with canvas.regions.placeRegion.
• Fixed issues with canvas.tokens.#getTokenData which threw errors when items or effect were empty.

Notes

• I wasn't really able to find a good spot for using canvas.tokens.#getTokenData and don't think it's relevant for this anyhow. We are also not using it anywhere in the system at present.
• This is a proof of concept for now while we discuss whether we want to add it to 0.11.

TODO

• Implement basic party sheet.
• Extend the Actor sidebar and implement game.actors.party as an easy access getter.
• Add setting to assign "primary party" with context menu options in the sidebar.
• Disallow creating (any?) items and effects on the party actor.

To test:

Create party actor and hero actor.

const party = await Actor.implementation.create({ type: "party", name: "Party" });
const hero = await Actor.implementation.create({ type: "hero", name: "Hero" });
await party.system.addMembers([hero]);
await party.system.placeMembers();

[JPMeehan]

1. RE: performTokenPlacement, we had previously discussed not wanting to do placeToken because it's more likely to be used by core
2. We already have DrawSteelActors as a subclass for game.actors, just need to add the access point
3. We've got metadata.invalidActorTypes on the item subclasses as us trying to more broadly accomodate module-added subtypes. I think that's probably sufficient?

[JPMeehan]

Should probably be DrawSteelSystemModel? I don't think it's super likely we end up with any pseudo collections but it does seem expected.

[JPMeehan]

I think foundry.utils.mergeObject(defaultData, data, { insertKeys: false, insertValues: false }) gets us equivalent results while being more maintainable?

[JPMeehan]

Do we want an a new field for this instead of overwriting the initialized TOF?

[JPMeehan]

I wonder if the array should be some static property on the constructor

[JPMeehan]

Why do we check if it's a valid member first? e.g. if I do a forced type update to turn a hero into an NPC I can no longer use this method to remove them.