bugfix: Updated FileSearchRanker to match change by OpenAI

[hiibolt]

Fixes issue mentioned in #340

[irbull]

I can confirm that if I use curl to access the create run endpoint, it also returns default-2024-08-21 which appears to be different from what the docs say. Since this appears to be an undocumented change, what do you think about using an alias instead of a rename, and supporting both default-2024-08-21 and default_2024_08_21. Just in case they break their API again.

Something like:

pub enum FileSearchRanker {
    #[serde(rename = "auto")]
    Auto,
    #[serde(alias = "default_2024_08_21")]
    #[serde(alias = "default-2024-08-21")]
    Default2024_08_21,
}

[hiibolt]

I can confirm that if I use curl to access the create run endpoint, it also returns default-2024-08-21 which appears to be different from what the docs say. Since this appears to be an undocumented change, what do you think about using an alias instead of a rename, and supporting both default-2024-08-21 and default_2024_08_21. Just in case they break their API again.

Something like:

pub enum FileSearchRanker {
    #[serde(rename = "auto")]
    Auto,
    #[serde(alias = "default_2024_08_21")]
    #[serde(alias = "default-2024-08-21")]
    Default2024_08_21,
}

I agree, I will link a commit tonight.

[hiibolt]

@64bit Could you look this change over? Because of the unprompted and undocumented spec change by OpenAI, crates currently depending on using the Assistants API fail even if they do not directly use this struct