[ramya18101]

🔧 Changes

Login analytics events (CLI - Auth0 - First Login and ... - As-User / ... - As-Machine) were sent with no extra properties, only version, os and arch. That made logins from short-lived CI jobs impossible to attribute: each fresh job gets a new install ID, and nothing on the event said which tenant it was for or whether CI, an agent or a person ran it.

Login events now carry the same attribution context that command-run events already have:

Property	Value
tenant	Domain just logged into
ci	true / false, from the existing CI environment detection
agent_client	Detected agent name, or empty
interactive	true / false, whether stdin and stdout are terminals

🔬 Testing

• New table-driven TestLoginTrackingProperties covers the tenant value, ci inside and outside CI, the interactive value, and that exactly four properties are sent.
• go test ./internal/analytics/ ./internal/cli/ passes, and golangci-lint reports no issues for both packages.

📝 Checklist

• All new/changed/fixed functionality is covered by tests (or N/A)
• I have added documentation for all new/changed functionality (or N/A)