Schedule Trigger - Data asset change in versions between deployment

### Describe your suggestion

Hi,

When a schedule is deployed to trigger an AML pipeline, and the latest data asset version at time of deployment is say version 1, then the schedule seems to always use version 1 of the data.

If there has been a change in the version, so the new latest version is for example version 2, in between schedule triggers, then the schedule does not seem to pick up the new version.

If it is possible to make the data asset version dynamic when deploying the schedule (so that whenever there is a change in the version it will always pick up the latest one), could you provide an example on how to do this?

Thanks!

### Additional details

_No response_

No file, test, or example entry point is named. Start by locating the Azure Machine Learning schedule deployment example for an AML pipeline and trace how its data asset version is selected; done means documenting or demonstrating whether a later data asset version is picked up between scheduled triggers.

Written by the indexing model from the issue text.