Add some checks when trying to join the same pool already joined

[emlowe]

Currently, if you are farming to a pool, and you join that same pool again, those transactions are merrily carried out on the chain even though this changes nothing for your farming.
Previous version would throw a cryptic error which was also a problem

This PR checks before creating any spends if the join pool URL is the same as the current pool URL
Fixes #7292

[coveralls-official]

Pull Request Test Coverage Report for Build 11716290246

Details

• 64 of 69 (92.75%) changed or added relevant lines in 4 files are covered.
• 39 unchanged lines in 9 files lost coverage.
• Overall coverage increased (+0.03%) to 90.962%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
chia/cmds/plotnft_funcs.py	7	12	58.33%

Files with Coverage Reduction	New Missed Lines	%
chia/full_node/pending_tx_cache.py	1	96.55%
chia/cmds/plotnft_funcs.py	1	17.52%
chia/wallet/util/wallet_sync_utils.py	1	86.07%
chia/wallet/wallet_node.py	4	88.18%
chia/full_node/weight_proof.py	4	90.48%
chia/server/ws_connection.py	4	88.1%
chia/server/address_manager.py	5	90.48%
chia/full_node/full_node.py	7	85.9%
chia/server/node_discovery.py	12	79.45%

Totals
Change from base Build 11710907999:	0.03%
Covered Lines:	102969
Relevant Lines:	112961

---

💛 - Coveralls

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

Conflicts have been resolved. A maintainer will review the pull request shortly.

[altendky]

Needs an import as well.

Suggested change

	with pytest.raises(ValueError, match="Already farming to pool"):
	with pytest.raises(ResponseFailureError, match="Already farming to pool"):

[Quexington]

Is there a reason this isn't WalletTestFramework?

[emlowe]

nothing in this file was using WalletTestFramework at the time, so I followed the conventions here. But I think your question is a good one and I'll look to convert it to use the newer concepts

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[github-actions]

This PR has been flagged as stale due to no activity for over 60 days. It will not be automatically closed, but it has been given a stale-pr label and should be manually reviewed by the relevant parties.