chore(ios): removed APSAnalytics framework and analytics stuff

[hbugdoll]

Introduction:

Ti.Analytics was removed by #13316 over three years ago.
For reasons of backward compatibility, some analytics-related code remained in the SDK.
Recently, some cleanups were done on the Android side (#14308 und #14310).

Description:

• fully removed unused APSAnalytics iOS framework, AnalyticsModule class and other code remnants
  • BTW an unused variable warning (-Wunused-variable) during SDK build process will disappear
• no need for <analytics>false</analytics> in tiapp.xml anymore

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	liveview@​1.5.6
	node-titanium-sdk@​6.1.0
	nodeify@​1.0.1
	lodash.merge@​4.6.2
	node-appc@​1.1.7
	markdown@​0.5.0
	lockfile-lint@​4.14.1
	moment@​2.30.1
	mocha@​11.7.4
	lint-staged@​16.2.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: npm xmldom allows multiple root nodes in a DOM CVE: GHSA-crh6-fp67-6883 xmldom allows multiple root nodes in a DOM (CRITICAL) Affected versions: <= 0.6.0 Patched version: No patched versions From: package-lock.json → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report