Add short doc on transactions

[cicdw]

This doc is imperfect, but hopefully establishes a good first step in documenting transactions. I'll continue to refine in follow up PRs if accepted.

[billpalombi]

I see that this deletes the page on retries. Is that intentional?

[cicdw]

@billpalombi yea that was intentional, I didn't see why retries needed their own page and the title felt overblown relative to the content.

[billpalombi]

yea that was intentional, I didn't see why retries needed their own page and the title felt overblown relative to the content.

Agreed on the title. I do think the Custom retry behavior, jitter, and global configuration content should live somewhere though.

I see at least two options:

• we could broaden the scope of the transactions page a bit and add it there.
• we could add to to the write tasks page (but its also relevant to the flows page)

[cicdw]

Yea agree those should be documented, there's just a small surface area - the task and flow pages make the most sense to me (and there are non-trivial distinctions in those docs - flows need to discuss infra retries, how task reruns are handled, etc). I can work on that doc next after I do another pass through of some caching functionality.

[billpalombi]

@cicdw are you already working on adding the retry content to the flow and task pages? If not, I will do that now. I don't want to forget that.

[cicdw]

@billpalombi nope haven't picked that up yet, take it away