Benchmark with pure-JS CRC32C implementations

[trivikr]

Describe the bug

The benchmarking is done against pure JS CRC32 implementation, although it calls it CRC32C

sse4_crc32/benchmark/single_fixed_size_buffer.benchmark.js

Lines 44 to 50 in 15cf479

	}, {
	title: 'JavaScript (table-based) CRC-32C',
	fn: () => jsCrc32(TEST_BUFFER, false)
	}, {
	title: 'JavaScript (direct) CRC-32C',
	fn: () => jsCrc32(TEST_BUFFER, true)
	}]

Steps to reproduce

replit https://replit.com/@trivikr/test-sse4crc32-benchmark
Online CRC32 calculator https://crccalc.com/?crc=123456789&method=crc32&datatype=ascii&outtype=hex

Code

const crc32 = require("crc32");
const sse4_crc32 = require("sse4_crc32");
const junderw_crc32c = require("junderw-crc32c");

const testString = "123456789";
console.log(crc32(testString).toString(16));
console.log(sse4_crc32.table_crc(testString).toString(16));
console.log((junderw_crc32c.str(testString) >>> 0).toString(16));

Observed behavior

In replit, the crc32 package returns CRC32 checksum instead of CRC32C checksum

Expected behavior

The benchmarking of CRC32C checksum by sse4_crc32 should be done against another pure-JS CRC32C checksum implementation like junderw-crc32c and not crc32

Additional context

I noticed this while writing my own CRC32 benchmark in https://github.com/trivikr/benchmark-crc32