feat: add autocapture for element clicks

[PouriaAmini]

Summary

This PR removes support for Android SDKs 18 and below.

This PR adds the Autocapture feature to enable automatically tracking clicks on clickable element for the legacy Android View system and Jetpack Compose. This functionality is available to both new and existing users but is disabled by default. To enable it, set userInteractions in DefaultTrackingOptions to true:

@OptIn(ExperimentalAmplitudeFeature::class)
Amplitude(
    Configuration(
        apiKey = AMPLITUDE_API_KEY,
        context = applicationContext,
        defaultTracking = DefaultTrackingOptions(
            userInteractions = true
        )
    )
)

Note: To use this feature, the @OptIn(ExperimentalAmplitudeFeature::class) is required to be added to the scope of the instance initialization, Activity class definition, or the entire file or module.

New automatically captured event

[Amplitude] Element Clicked: Emitted when a user clicks on a clickable element in the legacy Android View system or a tagged clickable @Composable functions in Compose.

Note: To capture the event in Compose, the clickable @Composable functions must include a Modifier.testTag, otherwise the event will not be captured. Clickable @Composable functions have an OnClick lambda or a Modifier.clickable modifier (for Jetpack Compose > 1.5).

New automatically captured properties

[Amplitude] Element Class: (Android Views only) The canonical name of the underlying class of the clickable element, or the simple name as given in the source code if the canonical name is unavailable.

[Amplitude] Element Resource: (Android Views only) The entry name for the resource identifier of the clicked element.

[Amplitude] Element Tag: (Compose only) The Modifier.testTag specified for the clicked @composable function.

[Amplitude] Element Source: (Android Views and Compose) The type of the origin of the clicked element, either "Android Views" for legacy Android Views or "Jetpack Compose" for Compose.

Checklist

• Does your PR title have the correct title format?
• Does your PR have a breaking change?: Yes

[justin-fiedler]

Hi @PouriaAmini the PR looks great.

I think we should do some testing in the wild with a small group of customers before enabling by default in production. Can you please make this feature (temporary) opt-in only?

[justin-fiedler]

Thanks @PouriaAmini. LGTM. I noticed the build/tests are falling though.

[Mercy811]

Thanks Pouria for adding element clicks autocaputre and using @ExperimentalAmplitudeFeature.