feat: add map type to scalar/array/expr

[xxchan]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

First part of #17743.

Design/background doc: https://www.notion.so/risingwave-labs/Map-type-788a6cb277de46669052683493a5d170

Only the data structures are implemented. (So it's not ready for users yet.) Other things, which should be done in the frontend, like literal syntax etc are left to next PRs.

Basically Map = List<Struct<"key":K, "value":V>>:

/// `MapArray` is physically just a `List<Struct<key: K, value: V>>` array, but with some additional restrictions
/// on the `key`.
#[derive(Debug, Clone, Eq)]
pub struct MapArray {
    pub(super) inner: ListArray,
}

#[derive(Clone, Eq, EstimateSize)]
pub struct MapValue(pub(crate) ListValue);

A minimal working example:

dev=> select map_from_entries(array['k1','k2'],array[1,2]);
┌──────────────────┐
│ map_from_entries │
├──────────────────┤
│ {"k1":1,"k2":2}  │
└──────────────────┘

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[xxchan]

• feat: support parsing map type: map(k,v) #17860 : 3 dependent PRs (#17864 , #17980 , #17986 )
• feat: add map type to scalar/array/expr #17690 👈
• refactor(types): simplify ArrayImpl::from_protobuf #17763
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @xxchan and the rest of your teammates on Graphite

[wangrunji0408]

Generally LGTM!

[xiangjinwu]

(posting some incomplete review comments first)

[xiangjinwu]

Short answer: we could rely more on FUNC_SIG_MAP when no rewrite needed but it wont unify all special rewrites. Actually PostgreSQL does some rewrites in the sqlparser yacc/bison file, which also feels pretty dirty.
https://github.com/postgres/postgres/blob/REL_16_3/src/backend/parser/gram.y#L14527-L14535

[BugenZhao]

L🥰TM