feat: pass through functions[].schedule property to ZISI

[netlify-team-account-1]

Related to

• feat: emit schedule property into manifest zip-it-and-ship-it#768.

This PR passes through the functions[...].schedule field to ZISI.

TODO:

• put change behind a feature-flag

[eduardoboucas]

Looks good! We'll need two additional things:

1. Add schedule to the list of function configuration properties (https://github.com/netlify/build/blob/main/packages/config/src/functions_config.js#L52-L58)

2. Add validation to the schedule property (see https://github.com/netlify/build/blob/main/packages/config/src/validate/validations.js) and accompanying tests

[ehmicky]

Not blocking this PR, but more of a general discussion: do you think we should just forward LaunchDarkly flags from @netlify/build to zip-it-and-ship-it? This would remove the need to do this type of PRs each time zip-it-and-ship-it needs a new feature flag.

[eduardoboucas]

Not blocking this PR, but more of a general discussion: do you think we should just forward LaunchDarkly flags from @netlify/build to zip-it-and-ship-it? This would remove the need to do this type of PRs each time zip-it-and-ship-it needs a new feature flag.

I'm not sure, to be honest. We're doing more than just passing flags through in normalizeFunctionConfig and I think having that level of control is a good thing.

I'd be more in favour of that if zip-it-and-ship-it was always called from Netlify Build, but that's not the case since CLI interacts with it directly. So I think it's good that zip-it-and-ship-it and Netlify Build have their own set of feature flags.

[eduardoboucas]

Looks great! I've added a couple of small comments, with the only blocker being the one about the test.

[eduardoboucas]

🎉