Move default options into the constructor

[heff]

In #1993 (diff) we discussed moving options into the constructor instead of on the prototype. Secondarily removing the this.options() accessor.

For the player we use the prototype options as global options for the player, but this could be done by providing a global options object that overrides the default when the player is initialized.

I'm not sure what impact removing the options() accessor would have, but right now it creates another source of truth, which isn't great. This would force us to be more specific about providing the info from options that we need.

@dmlap @gkatsev, are there places externally where we're relying on the options() getter?

Steps:

• Deprecate the use of component.options() (v5.0)
• Move all prototype.options_ uses into the constructor (5.x)
• Remove component.options() (v.6.0)

[heff]

Instead of attacking this completely in 5.0 I want to start the process by deprecating the use of component.options() and fixing the uses of it over time before removing it in 6.0. I think we use it a lot, especially in plugins, so trying to fix everything for 5.0 would be too much.

[dmlap]

People are definitely using the options() getter externally but I support deprecating it to avoid confusion over options versus properties. Pushing actual removal to 6.0 seems like a good move.

[heff]

#2229 checked the first box for deprecating options(). I added a check list item for moving prototype options into the constructor. Pushing this to 5.1.