[fix](doc) v3.x: fix ZH murmur_hash3_64_v2 example header and values

[boluor]

What

The v3.x ZH page for MURMUR_HASH3_64_V2 had its example result table copied verbatim from the non-v2 MURMUR_HASH3_64 page. Although the SELECT calls murmur_hash3_64_v2(...), the rendered table header showed murmur_hash3_64(NULL) / murmur_hash3_64('hello') / murmur_hash3_64('hello', 'world') and the values were the non-v2 results:

| murmur_hash3_64(NULL) | murmur_hash3_64('hello') | murmur_hash3_64('hello', 'world') |
|                  NULL |     -3215607508166160593 |               3583109472027628045 |

Fix

Mirror the already-correct v4.x ZH page — correct ..._v2 header and the actual v2 hash values:

| murmur_hash3_64_v2(null) | murmur_hash3_64_v2("hello") | murmur_hash3_64_v2("hello", "world") |
|                     NULL |        -3758069500696749310 |                  -662943091231200135 |

Verified live

Run on a master daily build (doris-0.0.0-2e72603618c):

select murmur_hash3_64_v2(null), murmur_hash3_64_v2("hello"), murmur_hash3_64_v2("hello", "world");
-- NULL | -3758069500696749310 | -662943091231200135

murmur_hash3_64_v2 is a deterministic hash, so the result is version-independent; v4.x ZH already shows these values.

Scope

ZH-only — v3.x has no EN murmur_hash3_64_v2 page. Backport of the ZH half of #3864 (dev) to v3.x; v4.x ZH was already correct, so no v4.x change is needed.

🤖 Generated with Claude Code