Avoid fetches for empty feature IDs

[schalkneethling]

Summary

Fixes #80 by preventing <baseline-status> from requesting WebStatus API URLs when the feature id is missing, empty, or whitespace-only.

What changed

• Normalize feature ids with trim() so values like " " are treated as empty.
• Sync the feature-id attribute alias to featureId in willUpdate() instead of updated().
• Guard the @lit/task fetch path so falsy normalized ids return before calling fetch().
• Add regression tests for no feature id, empty feature-id, dynamic feature-id updates, and clearing feature-id.

Why willUpdate()

Lit already handles attributeChangedCallback() for reactive properties, so this PR does not override it.

The alias sync belongs in willUpdate() because it computes state needed by the upcoming update. This also lets @lit/task see the normalized featureId before it checks its args and decides whether to run.

The previous updated() sync happened after render, and could schedule a second update. Moving the sync earlier keeps the behavior in Lit's normal lifecycle.

Test notes

The negative fetch tests use aTimeout(0) after updateComplete to give any async Task run attempt a chance to happen before asserting that no request was made.

The dynamic positive cases use waitUntil() to wait for the observable fetch count to stabilize rather than relying on a particular browser tick.

Validation

• npx eslint baseline-status.js test/baseline-status.test.js
• PATH=/Users/schalkneethling/.cache/codex-runtimes/codex-primary-runtime/dependencies/node/bin:$PATH npm test

All 11 browser tests pass.

[schalkneethling]

Heya @devnook - I was referred to you by @captainbrosset to ping for review here. I would also be more than happy to help with the process of triaging issues, managing dependency updates, etc., so let me know if there is a way to do this. Thanks!

[captainbrosset]

@atopal are you, or someone who worked on this codebase in the past, able to review this PR please? I've looked at it a bit, but would be more comfortable if someone who's worked on this could review. Thanks!