Update telemetry dependency constraint

[ChiragAgg5k]

Summary

• Relax utopia-php/telemetry from 0.4.* to ^0.4.
• Refresh composer.lock content hash for the root constraint change.

Why

Circuit breaker 0.3.1 uses the telemetry 0.4 lazy metric API. Keeping Utopia libraries on narrow telemetry constraints makes dependency alignment harder across the Appwrite stack.

Tests

• composer validate --strict
• composer lint
• composer test (fails in local environment because amqp:5672 is not resolvable)

[greptile-apps]

Greptile Summary

This PR relaxes the utopia-php/telemetry version constraint in composer.json from 0.4.* to ^0.4 and updates the composer.lock content-hash to match.

• The constraint change is effectively a no-op: in Composer, ^0.4 for a pre-1.0 package resolves to >=0.4.0 <0.5.0, the same range as 0.4.*. No package versions in the lock file changed.
• The composer.lock diff is limited to the content-hash field, confirming the resolved dependency graph is identical to before.

Confidence Score: 4/5

Safe to merge; the actual installed dependency set is unchanged and no runtime behavior is affected.

The only change is a constraint notation swap that resolves to the same version range, so there is no functional impact. The stated goal of relaxing the constraint to ease cross-library alignment is not achieved by this change, since ^0.4 and 0.4.* are equivalent for pre-1.0 packages in Composer.

No files require special attention; both changed files are purely declarative dependency metadata.

Important Files Changed

Filename	Overview
composer.json	Changes utopia-php/telemetry constraint from 0.4.* to ^0.4; both resolve to >=0.4.0 <0.5.0 in Composer, so the effective allowed range is unchanged.
composer.lock	Only the content-hash is updated to reflect the changed constraint string in composer.json; no package versions changed.

_{Reviews (1): Last reviewed commit: "Update telemetry dependency constraint" | Re-trigger Greptile}

[greptile-apps]

Constraint change is semantically a no-op in Composer

In Composer, ^0.4 for a pre-1.0 package resolves to >=0.4.0 <0.5.0 — exactly the same range as 0.4.*. The PR description frames this as "relaxing" the constraint, but the set of installable versions is unchanged. If the intent is to also allow 0.5.x or higher minor releases in the future without another constraint bump, a constraint like >=0.4 would be needed instead.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!