[Backport] Fix instances of -Wmissing-template-arg-list-after-template-kw.

Clang has a new warning that requires a template argument list after using
the template keyword. Remove uses of the template keyword when we're not
specifying types.

See llvm/llvm-project#94194 for the upstream
clang change.

Upstream-Status: Backport [chromium/chromium@b0088fa]
Bug: 344680447
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5604664
Reviewed-by: Kentaro Hara <[email protected]>
Reviewed-by: Daniel Cheng <[email protected]>
Commit-Queue: Amy Huang <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1311538}
Pick-to: 118-based
Change-Id: Icf1426fb718550346711b332ca658d92f1421064
Reviewed-on: https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/586001
Reviewed-by: Peter Varga <[email protected]>
(cherry picked from commit 0916f81)
Reviewed-on: https://codereview.qt-project.org/c/qt/qtwebengine-chromium/+/593503
Reviewed-by: Michael Brüning <[email protected]>

Author: amykhuang

chromium/third_party/blink/renderer/platform/wtf/hash_table.h

@@ -1639,7 +1639,7 @@ HashTable<Key, Value, Extractor, Traits, KeyTraits, Allocator>::ExpandBuffer(
     }
   }
   table_ = temporary_table;
-  Allocator::template BackingWriteBarrier(&table_);
+  Allocator::BackingWriteBarrier(&table_);
 
   HashTableBucketInitializer<Traits, Allocator, Value>::InitializeTable(
       original_table, new_table_size);
@@ -1693,7 +1693,7 @@ Value* HashTable<Key, Value, Extractor, Traits, KeyTraits, Allocator>::RehashTo(
   // This swaps the newly allocated buffer with the current one. The store to
   // the current table has to be atomic to prevent races with concurrent marker.
   AsAtomicPtr(&table_)->store(new_hash_table.table_, std::memory_order_relaxed);
-  Allocator::template BackingWriteBarrier(&table_);
+  Allocator::BackingWriteBarrier(&table_);
   table_size_ = new_table_size;
 
   new_hash_table.table_ = old_table;
@@ -1845,8 +1845,8 @@ void HashTable<Key, Value, Extractor, Traits, KeyTraits, Allocator>::swap(
   // on the mutator thread, which is also the only one that writes to them, so
   // there is *no* risk of data races when reading.
   AtomicWriteSwap(table_, other.table_);
-  Allocator::template BackingWriteBarrier(&table_);
-  Allocator::template BackingWriteBarrier(&other.table_);
+  Allocator::BackingWriteBarrier(&table_);
+  Allocator::BackingWriteBarrier(&other.table_);
   if (IsWeak<ValueType>::value) {
     // Weak processing is omitted when no backing store is present. In case such
     // an empty table is later on used it needs to be strongified.