Support BisonFi swaps without vote accounts for Jito bundles

Please add native support in Pallas and the OKX on-chain router for executing BisonFi swaps without including a vote account. My goal is to use Pallas for all routing and instruction generation, then assemble, sign, and submit the resulting transactions through Jito sendBundle while retaining BisonFi liquidity.

Currently, Pallas includes the vote account J1to1yufRnoWn81KYg1XkTWzmKjnYSnmE2VY8DGUJ9Qv in instructions for BisonFi routes. This also happens with a direct route and enableJit set to false. Jito rejects transactions containing this vote account, making these routes incompatible with bundles.

DFlow successfully executes swaps against the same BisonFi program and pool without this vote account. I verified two successful on-chain transactions through Solana RPC, including inner instructions and all accounts loaded through address lookup tables.

The OKX call uses a BisonFi instruction starting with 0x02 and passes 12 account entries, including the vote account. Transaction:
4gZEftw74iQ7j9DteTdFKiXxdD8YrXAureKWUMrbq9YtmFDjkVBtY4PfWerkusrayj6H5w4Ma92JDc4BjZX9Soo4

The DFlow call uses a BisonFi instruction starting with 0x07 and passes 9 account entries, without the vote account. Transaction:
2FNJzYBZu2axV2NfG5LdsDRW7T3MzNnoFXAWADGPvVM9vAPtubL1TsKeMoMHdMUiQShRWUJyjXMDoSdh2G85Li2y

Both calls use the BisonFi pool FJnaiidSLXFweWkgbinxEHRykVHsnkzDcYbNDR3RF5LN and complete successfully.

Please investigate the variant used by DFlow, or another supported BisonFi variant without vote accounts, and implement an equivalent native integration in Pallas/OKX. The required instruction format, account layout, authorities, and any caller-specific permissions should be confirmed with BisonFi. These examples do not establish that simply removing the account or changing one byte is sufficient.

The expected outcome is that Pallas-generated BisonFi swaps execute successfully and can be submitted through Jito without vote-account rejection, including applicable cyclic routes and JIT candidates. Excluding BisonFi or requiring an external DFlow integration would not satisfy this request.

Start by tracing the existing BisonFi route and instruction generation in Pallas and the OKX on-chain router. Compare the cited OKX and DFlow transactions, including their instruction variants and account layouts, then confirm the required format and permissions with BisonFi. Done means native Pallas-generated swaps work through Jito bundles, including applicable cyclic routes and JIT candidates.