Improve note commitment tree append performance

[teor2345]

Motivation

Alfredo and I have been doing some timing tests on Zebra's CommitBlock and CommitFinalizedBlock state requests.

In some of my tests, Sapling note commitment tree appends were taking multiple seconds to run.
This is probably due to the large number of new Sapling notes in the chain.

We should try to improve performance of this code.

Suggested Changes

Add benchmarks for:

• note commitment tree appends on random notes
• note commitment tree appends on large sprout, sapling, and orchard blocks (Add an NU5 block test vector that contains many shielded Orchard transactions #4774 & Add an NU5 block test vector that contains many shielded Sapling transactions #4775)
• note conversion to the correct type
• the inner functions that do the update, without acquiring the ReadWriteLock

Once we have benchmarks, try to improve the performance of the code:

• pass a vector to the append method, and do note commitment point conversions in parallel
• inline the functions that are called when appending note commitment trees

[teor2345]

Performance improvements are a low priority for Zebra at the moment.