fix(components): only treat gating args as evidence of configuration

[mgazza]

Follow-up to #4737, which I authored — a review after it merged found two flaws in the noise guard. The first is user-visible on a default config, so worth landing promptly.

1. Every non-GivEnergy user now gets a spurious warning on every startup

The guard counted every arg a component declares:

component_configured = any(configured_args.get(arg_info["config"]) for arg_info in component_info["args"].values())

gecloud_data declares the general-purpose days_previous (components.py:172), and the shipped apps.yaml:487 sets days_previous: [7] for everyone. So any user without ge_cloud_key — i.e. every non-GivEnergy user on a stock config — now sees this on every startup:

Warn: Skipping GivEnergy Cloud Data interface, missing required configuration: ge_cloud_data, ge_cloud_key

They never configured GivEnergy Cloud. That is exactly the noise #4737 set out to avoid, aimed at the whole user base — my mistake in the original PR.

Fix: restrict the check to the args that actually gate activation (required, required_true, required_or). Incidental shared settings no longer imply the user was setting the component up.

2. An empty credential stays silent, which is the case that most needs the warning

The guard tested truthiness, so a setting supplied as "", 0 or False counted as absent:

solis_api_key: ""

The required_or gate rejects the empty key, so Solis is skipped — and the guard also considers it unconfigured, so nothing is logged. A secret or environment substitution that unexpectedly resolves to an empty string is precisely when a user needs telling.

Fix: test key presence rather than truthiness.

Verification

Simulated every component in COMPONENT_LIST against the shipped apps.yaml:

• Before: gecloud_data warns. After: no component warns on a default config.
• A partly configured component still warns — e.g. an energy provider with its key set but its account id missing still reports missing required configuration: <key>.

Tests

The existing test is updated to cover both fixes rather than adding a new one:

• the silent case now also supplies an unrelated shared setting (days_previous), which would have failed under the old guard
• the warning case now uses an empty credential (solis_api_key: ""), which would have been silent under the old guard