Listing write steps for Core and Enterprise

[MeelahMe]

Closes #5878

Describe your proposed changes here.

Adding write steps for Core and Enterprise and describing the impact of flags and options on latency.

[MeelahMe]

Are these additions close to what you were looking for? @jstirnaman

[jstirnaman]

Are these additions close to what you were looking for? @jstirnaman

I like this and the detail explaining tradeoffs. IMO, the phrase "Key option" might be confusing. I would remove or replace it with a descriptive sentence.
I just merged a similar, but shorter variation of this - I wanted to add it to help explain no_sync in the API reference so I went ahead and copied it into /get-started. Sorry to step on your toes.

That said, /get-started is fairly bloated. I suggest we move this into a new page:

1. Merge your version and the Data flow section from content/shared/v3-core-get-started into a content/shared/influxdb3-internals-reference/durability page, following the pattern in https://docs.influxdata.com/influxdb3/cloud-serverless/reference/internals/durability/.
2. Remove all or most of the Data flow section from content/shared/v3-core-get-started and content/shared/v3-enterprise-get-started.
3. Link to the new page from /get-started and /write-data.

[jstirnaman]

Same here.

[jstirnaman]

This description doesn't fit the page--seems like it's for the influxdb3 CLI reference.

[jstirnaman]

The file path should be content/influxdb3/core/reference/internals/_index.md

[jstirnaman]

The file path should be
content/influxdb3/core/reference/internals/durability/_index.md