azurerm_data_factory_trigger_schedule supports schedule and description

[ms-henglu]

=== RUN   TestAccDataFactoryTriggerSchedule_basic
=== PAUSE TestAccDataFactoryTriggerSchedule_basic
=== CONT  TestAccDataFactoryTriggerSchedule_basic
--- PASS: TestAccDataFactoryTriggerSchedule_basic (213.63s)
=== RUN   TestAccDataFactoryTriggerSchedule_complete
=== PAUSE TestAccDataFactoryTriggerSchedule_complete
=== CONT  TestAccDataFactoryTriggerSchedule_complete
--- PASS: TestAccDataFactoryTriggerSchedule_complete (388.00s)
=== RUN   TestAccDataFactoryTriggerSchedule_schedule
=== PAUSE TestAccDataFactoryTriggerSchedule_schedule
=== CONT  TestAccDataFactoryTriggerSchedule_schedule
--- PASS: TestAccDataFactoryTriggerSchedule_schedule (213.27s)
PASS

[stephybun]

Thanks for this PR @ms-henglu, tests look good, just a few minor remarks and some suggestions for the docs. Once those are addressed then this LGTM 👍🏼

[ms-henglu]

@katbyte @stephybun Hi all, thanks for code review!
I've added a commit according to your suggestions, please take another look, thanks!

[katbyte]

Thanks @ms-henglu - LGTM 🍰

[github-actions]

This functionality has been released in v2.76.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.