[Feature]: Ability to bypass schedule for initial collection creation using schedule configuration paramaters

[DeftNerd]

Is your feature request related to a problem? Please elaborate.

I like having collections of festival award winning movies, but those festivals occur yearly.
In my configuration, I like to have a yearly schedule that occurs after the awards are announced. I would prefer not to manually override the schedule to create the collection for the first time and then schedule it afterwards.

For example, the git: PMM/award/cannes configuration file doesn't have a schedule embedded in it, so my PMM config says:

      - git: PMM/award/cannes
        schedule: yearly(06/01)

The Cannes awards are issued at the end of May every year.

The problem is that if I run this today, it's after 06/01 so the collection won't be created until next year. I've missed the opportunity.

Describe the solution you'd like

I would like to see an additional scheduling option to add to the existing ones like hourly, daily, weekly, never, range, etc. Perhaps it could be called create or onEmpty. Whatever nomenclature seems to be already used in other areas of PMM.

The idea would be that we could embed the schedule information within config files (especially GIT based ones) that are shared so when someone wants to add an awards show, when PMM is run it'll create the collection and process the data and then it won't be run again until the other schedule criteria is met.

For Example:

    schedule: 
     - onEmpty
     - yearly(06/01)

Additional Information

No response