New Tasks Scheduler - Schedule the Task

## ACs

- The second substep on the "Schedule a Task Page" is "Schedule the Task" (See Figma)
- Display the text "Schedule the Task" underneath the select a script dropdown
- Below the "Schedule the Task" text, display the text "Set the interval at which the task runs and an optional time delay."
- Below that text should be the "Every" and "Cron" tab options. See Figma.
- Below that, display the "Every" and "Offset" text and input boxes
- The "Every" input should have a red asterisk to the right of it indicating that it's a mandatory field
- Both the "Every" and "Offset" input text should have a grey question mark tooltip to the right of it so that the users can learn more about those fields.
- The tooltip text expected for the "Every" question mark is: "The is the interval at which the task runs. It also determines when the task first starts to run, depending on the specified time (in duration literal). [Learn More](https://docs.influxdata.com/influxdb/cloud/process-data/task-options/#every)
- The tooltip text expected for the "Offset" question mark is: "Offset delays the execution of the task but preserves the original time range. [Learn More](https://docs.influxdata.com/influxdb/cloud/process-data/task-options/#offset).
- There should be examples of the expected values inside the "Every" and "Offset" input boxes so that the user knows what's expected of them. For example 3h30s or 20m
- If the user chooses the "Cron" tab, then display the "Cron" text and input field.
- Cron should have a red asterisk to the right of it indicating that it's required
- Cron should also display a grey question mark tooltip. Text expected for the "Cron" tooltip is: Cron is an expression that defines the schedule on which the task runs. Cron scheduling is based on system time. [Learn More]
- Next to the cron input field should be an Offset input field with the same tooltip as the Offset input field in the 'every' flow.
- (https://docs.influxdata.com/influxdb/cloud/process-data/task-options/#cron).
- Inside the "Cron" input box, display an example of the data type expected (String): 02***
- Add data validation on all schedule task input fields for both every and cron so that the user doesn't try to add values that don't work. Use existing data validation.

## Implementation
- Figma for scheduling via "Every" https://www.figma.com/file/r91KxurPL3VQ7JMqc9Ldqo/New-Tasks-Experience?node-id=1669%3A34509
- Figma for scheduling via "Cron" https://www.figma.com/file/r91KxurPL3VQ7JMqc9Ldqo/New-Tasks-Experience?node-id=1677%3A33902
- When Figma designs show Clockface 4 components - don't worry about using Clockface 4 if it's not ready by implementation time. Just use the Clockface component and when Clockface 4 drops, these will automatically get updated