feat: add customer origin url fallback

[AmeanAsad]

Changes:

• Simplified options passing to only use a nodes array instead having (nodes, url, node) as accepted options.
• Added a fallback to an originURL if it exists to fetch data as a final fallback.

[guanzo]

Is there a way to document the fetch options in a DRY way similar to typescript, but with our current tooling?

const fetchOpts: object = {
   cdnURL: string,
   // etc
}

The amount of potential options has grown and I feel the jsdoc method of listing individual fields is getting a bit hefty, especially since there's multiple methods that accept the same options object.

EDIT: I guess @typedef is the way. https://jsdoc.app/tags-typedef.html

[guanzo]

This will still return 'car' when we pass { format: null }. Now i'm wondering if it's better to create a client side only 'flat' format to avoid falsy checks defaulting to 'car', when in fact we want flat files.

[AmeanAsad]

Addressed this.

I think adding explicit file formats is better to identify flat or car. We only currently support car or flat though so I think the condition here is sufficient and we can change this later if needed if we start supporting more file formats.

[guanzo]

we'll eventually need to support raw format too.

[AmeanAsad]

Do you want me to handle the file types explicitly in this PR or shall we do that later?

[guanzo]

lets do another PR, this PR is too big already