[Feature Request] Have the Active Effects' Status Conditions dropdown apply the status conditions separately rather than "embed"

[Krigsmaskine]

The current situation "embeds"/makes the system consider the activeEffect as the chosen status condition(s) in the dropdown. I argue that is counter-intuitive and goes against the (assumed) design of the status conditions/effects. I will most likely use status conditions/effects interchangeably, bear with me.

I find the whole point of status effects that they're universal, visual and recognizable from the canvas. With the current situation, the only way to find out a token with the activeEffect is "also" affected by the selected status conditions is to open that token's character sheet, if you don't recognize the activeEffect's icon as being one of those activeEffects with x, y or z added as a status condition.

• This is not feasible for players the vast majority of the time, as they don't own the tokens' they're attacking.
• Even if it's an actor the player owns, such as their player character, everything they traditionally use in combat are on different tabs than the active effect tab/status condition tab.
• Sometimes activeEffects from items can apply their own active effect and then also apply a status condition, but they're not necessarily interlinked. Having the status condition applied separately means it'd be easy to dismiss it from the token hud (right-click remove).
• It's not ideal for neither GM or players to get a quick overview of what's currently happening in the scene for playing their turns. You want it to be quickly evident who is Prone, who is Paralyzed and other similar status conditions that change how the dice are rolled for people who do not own the token, too.

[JPMeehan]

Worth noting that this is related to core handling — that statuses field is defined by the BaseActiveEffect schema.