test: convert Google Gemini tests to VCR

[codefromthecrypt]

part of square/exchange#67 closes square/exchange#71

[codefromthecrypt]

@baxen I'll move each pending PR from exchange to here one-by-one, here's the first!

[codefromthecrypt]

There are a lot of IDE warnings about call sites we use, as it is at the moment tools: Tuple[Tool]. So, this clears warnings about passing None. Though I wonder if it shouldn't be tools: Tuple[Tool, ...]? Seems that would be more explicit about possibly none, and also clear some other warnings. If you feel this is worthwhile I can in a follow-up or different PR.

[codefromthecrypt]

#149

[lamchau]

:nit: could we format the json so it's easier to read?

        string: |-
          {
            "candidates": [
              {
                "content": { ... }
               }

[codefromthecrypt]

@lamchau

:nit: could we format the json so it's easier to read?

technically yes, it will require some engineering to write a custom serializer as vcr has no options built-in. I'm not opposed to this, but it also will affect the openai data already here, and could be done as a separate task. Is it ok if we decouple this? You can assign that issue to me which I can try on a weekend or a flight.

[lamchau]

@codefromthecrypt sure! just a nit - i just like to know what's being passed in

just for learning: is the custom serializer required to dump the request/response to yaml? never used it before so i was naively thinking using a yq transform for post-processing - the serializer sounds much more robust (and involved)

edit: made issue #127, can't seem to assign it - thanks for taking a look!

[baxen]

Looks great!

[codefromthecrypt]

@lamchau

just for learning: is the custom serializer required to dump the request/response to yaml? never used it before so i was naively thinking using a yq transform for post-processing - the serializer sounds much more robust (and involved)

So, I didn't consider yq (like something we could do in just format), it is possible that doing that wouldn't taint the input expectations vcrpy and look like request drift. That could be the easier way out vs a custom serializer, which is the current suggestion from the project. kevin1024/vcrpy#580