WIP feat: move to v13

[marvin9257]

• Please check if the PR fulfills these requirements

• We use semantic versioning (https://github.com/semantic-release/semantic-release to be specific), so follow https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines
• Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  features and refactor for AppV2

• What is the current behavior? (You can also link to an open issue here)
  system incompatible with v13
  system uses Dialog (v1)
  system uses ItemSheet (v1)
  AdvancedSettings uses AppV1
  getChatLogEntryContext Hook no longer present in v13
  Actor Sheets use AppV1
  Consumables and Attachment list reset to default on update
  AP Values are only numbers
  Can't drag-drop AE's
  Dialog's still use jQuery
  Macro Compendium uses DialogV1
  ActorSheet items are sorted by a handlebar helper
  Can't drag-drop a folder
  Can enter non-unique skill names,
  No way to drag multiple items that aren't in one folder
  Only PSI and ALT characteristics can be hidden if zero

• What is the new behavior (if this is a feature change)?
  system mostly runs with v13
  refactor to use DialogV2
  refactor to ItemSheetV2
  refactor AdvancedSettings to ApplicationV2
  refactor to TwodsixChatLog that extends core ChatLog and ChatPopout (not mixin?)
  Actor Sheets now use app v2
  Remove default for consumable lists and preserve state across refresh. All lists initialize to collapsed on first open.
  AP values may be formulas
  Limited ability to drag-drop Active Effects
  Move all JQuery references in Dialogs to DOM
  Move macros to DialogV2
  Actor sheet items are sorted in sheet _prepareContext()
  Allow ability to drag-drop item folders
  Try to make skill names unique by appending number if needed (this is so that skills proxy works correctly)
  Add @ItemList enricher to drag multiple items from items sidebar
  Allow EDU, SOC and INT characteristics to be hidden if zero.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
  YES, data migration is one way and older chat message will not function.

• Other information: