Glide-Core: Refactor and cleanup value_conversion.rs

[acarbonetto]

Describe the feature

Our value_conversion.rs file contains duplicate code and some unspecified/generic implementation logic. We should refactor typings to cover duplicate code and be as specific as possible for type (for example: bulk string vs simple string).

From discussion: #1816 (comment)

Use Case

Currently, we have the following types available:

#[derive(Clone, Copy)]
pub(crate) enum ExpectedReturnType<'a> {
    Map {
        key_type: &'a Option<ExpectedReturnType<'a>>,
        value_type: &'a Option<ExpectedReturnType<'a>>,
    },
    MapOfStringToDouble,
    Double,
    Boolean,
    BulkString,
    Set,
    DoubleOrNull,
    ZRankReturnType,
    JsonToggleReturnType,
    ArrayOfStrings,
    ArrayOfBools,
    ArrayOfDoubleOrNull,
    Lolwut,
    ArrayOfStringAndArrays,
    ArrayOfArraysOfDoubleOrNull,
    ArrayOfMaps(&'a Option<ExpectedReturnType<'a>>),
    StringOrSet,
    ArrayOfPairs,
    ArrayOfMemberScorePairs,
    ZMPopReturnType,
    KeyWithMemberAndScore,
    FunctionStatsReturnType,
    GeoSearchReturnType,
    SimpleString,
    XAutoClaimReturnType,
    XInfoStreamFullReturnType,
}

We should divide and organize types based on common uses. For example, we have a lot of ArrayOfX types, which could take advantage of recursive typing like we now have for Maps. Array { element_type: type } could replace all of these.

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

Client version used

All

Environment details (OS name and version, etc.)

All