Allow state icons to be rendered places other than on top of token

[dstein766]

Is your feature request related to a problem? Please describe.
Currently, state icons MUST and CAN ONLY be super-imposed on top of a token.

Describe the solution you'd like
With the introduction of overlays, it would be desirable to decouple the display of state icons from (only) tokens. At least two additional features for state icons are desired:

1. Allow setState to specify a target for where the state icon should be rendered. Example: setState("blah", 1, tokenID) or setState("blah", 1, overlayName)...and perhaps even setState("blah",1, <list_of_targets>)
2. Allow states to be set w/o forcing ANY display of a state icon. Example: setState("blah", 1, <list_of_targets>)

Describe alternatives you've considered
In order to render states places other than tokens, or to prevent states from rendering on tokens, it is currently necessary to maintain a "shadow" state system which avoids use of the existing setstate/getstate commands, and also avoids referencing the State table in Campaign Properties.

Additional context
This proposal would also be enhanced by the existing proposal to track state duration.

[dstein766]

Oops. GitHub formatting mangled my bullet point #1. The last sentence should read "...and perhaps even setState("blah",1,list_of_targets)

[bubblobill]

I often use the option for States to only display on hover as I find they tend to clutter the view.
I would like to see the ability to offset them to outside the token footprint.
An option to set them to not display at all would allow you to store the state image in the campaign properties for access by an alternate viewing method.