Update the trouble shooting guide to include a brief description on uncles, how they can affect users, and how to tell if your bundle has been uncled

[Robert Miller]

If a user's bundle was:

• Unbundled
• A tx was included in another searchers bundle
• had txs included when reverting

Then they should check for uncles. The problem is that when transactions are uncled they are both propogated in blocks as well as emitted into the public mempool by clients. Thus, bundles can become publicly known through being uncled. The rough steps here are:

• Go to the txn on Etherscan
• Go to the block the txn was mined in. Check that block for uncles.
• Check the previous 6 blocks for uncles

If uncle(s) are found then:

• Go to Alchemy Composer and plug in the block hash for each uncle. Example link
• Check the transactions for the affected transaction(s) by searching for the transaction hash
• If this was found then your transaction was definitively uncled
• If it was not found then your transaction might still have been uncled, but we don't know for sure (e.g. your bundle could have been included in a child of an uncle, which would not be included in protocol)

[George Zhang]

Uncle is not relevant any more.

@bertmiller let's close this issue