Refactor strategy foundation

[piitaya]

Proposed change

This PR changes the way to define strategies. original-states and energy strategies has been migrated to the new API.

Dashboard and view strategies has been split into 2 class. This class share the same interface so we can easily extends it to other elements (section within a view for example). Also a config editor can be easily added by adding getConfigElement method to the class (#17916 will be edited with this changes)

Config format

The options has been moved to the root (to be consistent with card config). Backward compatibility for current custom strategies has been added with a drawback : options property can not be used.

Before

strategy:
  type: original-states
  options:
    foo: bar
views: []

After

strategy:
  type: original-states
  foo: bar
views: []

Generate method parameters

• config: the user configuration of the strategy with options.

  { 
    type: "energy",
    show_date_selection: true
  }

• hass: Home Assistant object
• params: custom parameters injected by the frontend (e.g. narrow)

Before

class DemoStrategy {
    static generateView({
        view,
        config,
        hass,
        narrow
    })
    static generateDashboard({
        config,
        hass,
        narrow
    })
}

After

class DemoDashboardStrategy {
    static generate(config, hass, params)
}

class DemoViewStrategy {
    static generate(config, hass, params)
}

Note

I kept the custom element registry for storing the strategies (and custom ones) even if it's not valid because it will be easier for developer to have similar way to register strategies than cards.
A backward compatibility has been added to avoid issues with custom strategies that are not using the new format.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io