fix: 🐛 double method definitions and python2 syntax

[lbillinghamwrk]

GhConf run https://github.com/optile/ghconf-runner/actions/runs/16501328390/job/46660454633
fails with NameError: name 'unicode' is not defined.

Unsurprisingly, as that hasn't been valid python syntax in more than 5.5 years.

That invalid syntax was in 2 functions both of which were redefinitions of earlier, valid callables.
This PR removes the invalid syntax, we should now have the valid callables in the method resolution order.

Goodness knows how this ever worked. Clearly there is no test coverage here.
We must either have never hit the {replace,remove}_team_push_restrictions functions before, or only hit them is circumstances where assert lines are swallowed (needs python compiler/interpreter to be compiled with unusual optimization flags)

Relates to PCPAY-3844 and https://app.incident.io/payoneer-checkout/incidents/362

[lbillinghamwrk]

thought: Dear reviewer, you probably want to expand the diffs around the "we want this" so you can verify that the {replace,remove}_team_push_restrictions versions that we want to keep are indeed valid syntax

[lbillinghamwrk]

thought: I tried running a linter with reasonable defaults over this codebase, there are a huge number of errors. However, none are F821 Undefined name or SyntaxError raising

[lbillinghamwrk]

thought: python 3.9 is what we use in ghconf-runner. That is only known current user of this code.

So we lint, docs, and typecheck on that

[lbillinghamwrk]

@jonathan-schmieg I think we should use your admin powers to force merge this PR.

There is no chance that I'm getting CI to pass for this fork.
The minimal change to get the test suite to start running is in #32, we are seeing tonnes of failures there for changes unrelated to cleaning up the python2-only NameErroring code.

GhConf is broken and I'm 99% sure that this PR will make it less broken if merged.

I guess previous maintainers of this fork just force merged rather than running PRs with check suites.

Especially since the last commit to the branch fixed completely invalid syntax that had been around for years
ce95301