Gmail: restructure

[josephjclark]

@decarteret I've done a little restructure here with the following changes:

• Adaptors.js now only contains user facing Operations
• Utils.js contains all the support

I know a lot of our adaptors don't look like this, but it's a pattern I'm trying to push us towards. I think it's just neater.

In addition I've made a couple of little tweaks:

• I've added expandReferences to the top of getContentsFrom Messages
• I've removed some code that it unused (like the request function, which is generated for you in the original template)
• I've removed unused unit tests

The expandReferences thing is what makes lazy state ($) work. Basically it means users can pass a function as an argument, and that function will be called by the adaptor, with the latest state, to get a value for that argument. This is really important to enable users to pass values from state into queries

I haven't tested any of this, but your test workflows should all work without any changes. Please check and then merge this down 🙏

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI

You can read more details in our Responsible AI Policy