Randomize anti-fee sniping height

[notmandatory]

"When possible to use anti fee-sniping, you always set the current height. All implementations of anti fee-sniping i'm aware of randomize this by sometimes using a much lower height (typically 100 less) to avoid consistently giving up the height at which a transaction was crafted. I'm not sure how useful this randomization is, but you might want to consider it. Especially as you already have a RNG at hand in this function."

[aagbotemi]

Hi @notmandatory

The description of randomizing anti-fee sniping height is mentioned in BIP326. Do we want to limit anti-fee sniping height to only taproot transaction or we implement it for all transactions?