Dynamo to S3 Sample DAG and Docs

[ferruzzi]

Adds a sample DAG and docs for the existing Dynamo to S3 Transfer operator.

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[ferruzzi]

@eladkal - Another short one in the DAG/Docs improvement project if you get time, since you reviewed the previous ones.

[ferruzzi]

Failing image build; rebased

[eladkal]

Can you please extend the example/docs to include also the segment explanation?

airflow/airflow/providers/amazon/aws/transfers/dynamodb_to_s3.py

Lines 65 to 87 in 602abe8

	To parallelize the replication, users can create multiple tasks of DynamoDBToS3Operator.
	For instance to replicate with parallelism of 2, create two tasks like:
	.. code-block:: python
	op1 = DynamoDBToS3Operator(
	task_id="replicator-1",
	dynamodb_table_name="hello",
	dynamodb_scan_kwargs={
	"TotalSegments": 2,
	"Segment": 0,
	},
	...,
	)
	op2 = DynamoDBToS3Operator(
	task_id="replicator-2",
	dynamodb_table_name="hello",
	dynamodb_scan_kwargs={
	"TotalSegments": 2,
	"Segment": 1,
	},
	...,

(and remove the segment example from the comments)

[ferruzzi]

These changed should be in b0278a1

[github-actions]

The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest main or amend the last commit of the PR, and push it with --force-with-lease.