Trader tool: OAuth support, match mods by tradeHash (fixes many local and essence mods), add price sorting, add radius jewels, notice when rate limited

[vaisest]

Fixes #1409, #1314, #748, #993, #1667, #185, #1748

• Trade search: Ignoring Block Chance searches #1409 somehow
• add the new feature of instant buyout at the "trade for these items" search tab #1314 this is already fixed, but this adds relevant options
• Trade whisper alternative for console player #748 for instant buyout
• "Trade for these items" selects wrong stat filter on trade site for stat with multiple stat filters (e.g., accuracy) #993 by finding trade site mods using tradeHash
• Trade Whispers Greyed out (not able to trade) #1667 with the search for button
• Local Mods Don't Work in Trader #185 should be fixed. Not tested but the trader uses tradeHash now
• Armour is using wrong stat filter in item search #1748

#469 might be related

Description of the problem being solved:

• Ports PoB1 trader improvements
• Fixes mod weight generation, where for example some local modifiers were not correctly generated as PoB does not internally use the (local)
• Fixes radius jewels and improves the jewel search in general by removing the any option, which would have caused poor results due to the lack of available filters
• Uses OAuth header instead of poesessid. Handling logins in different view is solved by putting the PoEAPI instance in main.
• Uses poe.ninja currency page endpoint for currency data
• Adds a countdown when rate limited to clarify why the tool is being slow. The rate limits for Oauth seem to be more strict, which means the tool waits more overall.

Most of these changes could probably be ported to pob1 for consistency.

Steps taken to verify a working solution:

• Previous test suite passes without errors
• No new tests were written, but relevant tests were fixed to pass

Possible issues

I had problems with 429 rate limiting. I'm not sure if that's because of me mashing f5 to test changes, or a real issue.

Issue was caused by Cloudflare, fixed by GGG.

Radius jewels don't generate a weight for the mod that increases the radius. I'm not sure how this should be generated as its value depends purely on the other mods on the jewel. This only affects the weighted sum, though. I'm not sure if it's worth paying attention to. For my build, it's sort of useless, but if it has a large impact, we could assign a manual weight to it to not exclude it from the weighted sum. In the sorting done in PoB, it is taken into account.

Some modifiers don't seem to get tested. I don't think this is a trader issue, but rather that GGG hasn't assigned spawn weights to some mods. For example, the jewel resistance corruptions only have a default tag. This seems to have been a problem in the past too as seen in #1269.

Link to a build that showcases this PR:

Nothing specific, but:

• Adorned build with max jewel sockets: https://pobb.in/DQRTp6Pz5sTM
• My build: https://pobb.in/_5dn99Q_Os69

Before screenshot:

(not sure why the previous version doesn't work at all)

body:

amulet:

After screenshot:

body:

amulet:

In search results it should also be clear that more mods are generated. For example a lot essence mods and local-only mods were previously missing which made results very bad.

Depends on #1830

[vaisest]

I don't know what this is exactly referring to, but its fix causes another crash

[Wires77]

Looks like this behaviour is what it's referring to:

[vaisest]

Back to draft for now as the changes from the comparison PR need to be fixed here