fix: fix web attribution identify and session start order

[yuhao900914]

Summary

Original Issue:
The campaign tracking fired after the session start event, so the session start event won't have the web attribution identify, which led to the Channels related to sessions being wrong.

Related Tickets:
https://amplitude.atlassian.net/browse/AMP-96571
https://amplitude.atlassian.net/browse/AMP-95820

• move the web attribution logic into the analytics-client-common
• create WebAttribution class and group the web attribution logic in.
• call webAttribution track in setSessionId and in process(xx)
  - make setSessionId async and add several await to keep the order.

Checklist

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

[omares]

Hey @yuhao900914, since we're affected by this issue, I would like to understand the solution which has been applied. I would appreciate it if you could elaborate on that.
I'd also like to understand why the changes haven't been applied to the web attribution browser plugin. Instead, it seems the code has been duplicated.

[yuhao900914]

Hey @yuhao900914, since we're affected by this issue, I would like to understand the solution which has been applied. I would appreciate it if you could elaborate on that. I'd also like to understand why the changes haven't been applied to the web attribution browser plugin. Instead, it seems the code has been duplicated.

Hi @omares , Thanks for your support. Previously, fire session end and session start events were bundled together, the web attribution was a plugin, and when to execute the web attribution plugin had a specific order. This makes it impossible to fire a web attribution to identify the call in the middle of the session end and session start event.

[izaaz]

@yuhao900914 on the summary, can you please also describe the problem that we are trying to solve?

[izaaz]

A couple of minor comments but the rest looks good. Thanks @yuhao900914