fix(reverseGeocoder): abort ongoing requests if a new reverse geocode request comes in

[dopenguin]

Summary

As the title states, reverse geocoding is now being aborted once a new request comes in. If this were not to be added, I could e.g. drag the pin around a few times and the map would keep centering on ALL position.

Instructions for local reproduction and review

Drag the pin around a few times in iceberg. It should now only center the map on the last position.

[github-actions]

PR Preview Action v1.8.0
🚀 View preview at https://Dataport.github.io/polar/pr-preview/pr-571/
Built to branch gh-pages at 2026-04-22 14:48 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[oeninghe-dataport]

🏓 @dopenguin

[dopenguin]

🏓 @dopenguin

🏓 @oeninghe-dataport

[warm-coolguy]

🏓 @dopenguin @oeninghe-dataport I closed the prior thread; if that pattern is to be changed, it should happen globally as a separate effort as proposed, and should prior to change be discussed in our Weekly.

Skimming the code, I found various instances of signal.aborted checks that were, in other spots, used to prevent spamming the console. I propose this technique is used here, too, to avoid confusion regarding "unerroring errors" further down the line.

[dopenguin]

🏓 @dopenguin @oeninghe-dataport I closed the prior thread; if that pattern is to be changed, it should happen globally as a separate effort as proposed, and should prior to change be discussed in our Weekly.

Skimming the code, I found various instances of signal.aborted checks that were, in other spots, used to prevent spamming the console. I propose this technique is used here, too, to avoid confusion regarding "unerroring errors" further down the line.

So you propose moving the AbortController from the util to the store and passing the signal to the utility function?

🏓 @warm-coolguy @oeninghe-dataport

[warm-coolguy]

🏓 @dopenguin @oeninghe-dataport I closed the prior thread; if that pattern is to be changed, it should happen globally as a separate effort as proposed, and should prior to change be discussed in our Weekly.
Skimming the code, I found various instances of signal.aborted checks that were, in other spots, used to prevent spamming the console. I propose this technique is used here, too, to avoid confusion regarding "unerroring errors" further down the line.

So you propose moving the AbortController from the util to the store and passing the signal to the utility function?

🏓 @warm-coolguy @oeninghe-dataport

Yes, please.

🏓 @dopenguin

[dopenguin]

🏓 @dopenguin @oeninghe-dataport I closed the prior thread; if that pattern is to be changed, it should happen globally as a separate effort as proposed, and should prior to change be discussed in our Weekly.
Skimming the code, I found various instances of signal.aborted checks that were, in other spots, used to prevent spamming the console. I propose this technique is used here, too, to avoid confusion regarding "unerroring errors" further down the line.

So you propose moving the AbortController from the util to the store and passing the signal to the utility function?
🏓 @warm-coolguy @oeninghe-dataport

Yes, please.

🏓 @dopenguin

Been there, done that b032ba5

🏓 @warm-coolguy