fix(autocapture): prioritize autocapture over deprecated defaultTracking

[tmchow]

Summary

Attribution, pageViews, sessions, fileDownloads, and formInteractions now correctly use config.autocapture instead of only checking the deprecated config.defaultTracking property. Falls back to defaultTracking for backwards compatibility when autocapture is undefined.

Fixes #1369

Checklist

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

[tmchow]

I had issues with a previous PR I submitted #1360 and at that time @Mercy811 suspected it was due to me not having permissions to the credential vault. They said:

It seems that GitHub blocks access to secrets for security reasons (to prevent malicious PRs from stealing secrets) a pull request from a forked repository.

So someone in Amplitude team with correct access needs to create a new PR and cherry pick the commits please 🙏

[Mercy811]

@tmchow it was because the or was made from a forked repo. If you could just clone, it should work

[tmchow]

@tmchow it was because the or was made from a forked repo. If you could just clone, it should work

@Mercy811 I'm running into issue as I'm getting permission errors about being able to push to this repo though....this is why I created a fork. Meaning, I can't even push a branch up to origin.

[tmchow]

@daniel-graham-amplitude are you able to help? I don't think I have the right permissions in this repo, so someone who does needs to open a new PR and cherry pick my commits to shepherd this through.

[daniel-graham-amplitude]

@tmchow yes definitely! I'll have a look at this either tonight or first thing tomorrow.

[tmchow]

@tmchow yes definitely! I'll have a look at this either tonight or first thing tomorrow.

Thanks @daniel-graham-amplitude !

[Mercy811]

Hi @tmchow the fallback logic is supported already. I don't think your fix here (fallback to default tracking when autocapture is undefined) will fix the issue (autocapture.attribution doesn't work)