Stabilize scheduled CI by making Supertrend description assertion case-insensitive

[Copilot]

The scheduled Tests workflow failed due to a brittle assertion in tests/indicators.test.ts that expected exact capitalization for the Supertrend indicator description. TradingView returned semantically identical text with different casing (strategy vs Strategy), causing a false negative.

• Root cause

  • Indicator metadata casing changed upstream ("Supertrend Strategy" → "Supertrend strategy"), while the test required exact string equality.

• Change

  • Replaced strict equality with a case-insensitive full-string match for the Supertrend description.
  • Scope is intentionally limited to the single failing assertion.

• Why this shape

  • Keeps validation strict on content (Supertrend strategy) while removing non-functional casing brittleness.

// before
expect(indicators.SuperTrend.description).toBe('Supertrend Strategy');

// after
expect(indicators.SuperTrend.description).toMatch(/^Supertrend strategy$/i);