chore(points): add track points event to transaction watcher

[kathaypacific]

Description

In case the transaction is not settled within the same app session, we should add the points tracking to the transaction watcher as well.

I added the network to the tracked event, in preparation for network specific activities.

Test plan

n/a

Related issues

n/a

Backwards compatibility

Y

Network scalability

If a new NetworkId and/or Network are added in the future, the changes in this PR will:

• Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.35%. Comparing base (d35a51b) to head (a96f4a4).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5441   +/-   ##
=======================================
  Coverage   86.34%   86.35%           
=======================================
  Files         756      756           
  Lines       31266    31271    +5     
  Branches     5376     5378    +2     
=======================================
+ Hits        26998    27004    +6     
+ Misses       4035     4034    -1     
  Partials      233      233           

Files	Coverage Δ
src/points/types.ts	100.00% <ø> (ø)
src/swap/saga.ts	94.35% <ø> (ø)
src/transactions/saga.ts	58.59% <100.00%> (+2.01%)	⬆️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d35a51b...a96f4a4. Read the comment docs.

[jeanregisser]

What do you think of using NetworkId to remove any ambiguity?

[kathaypacific]

yes fair, i updated to use networkId. i thought i was saving some computation by using the network but i was mistaken (reading the wallet code i thought that we need only the network to create the viem client, but we've a couple of layers of mappings in between!)