d3d12: Fix incorrect hash table usage
I'd assumed that since insert didn't take a deleter, it was find-or-insert, not insert-or-replace. This caused a bo reference leak if the same bo was used more than once in a batch.
Fixes: fde36d79 ("d3d12: Don't wait for GPU reads to do CPU reads")