Issue # (if applicable)

Tracking: #31785

Reason for this change

The targetOverrides prop is adding confusion to the API as it override what is set on the target. A better way to reuse target props would be:

const targetBaseProps = { input: ...someInput... }

const schedule1 = new Schedule(this, 'Schedule', {
    scheduleExpression: ScheduleExpression.cron({ day: '20' }),
    target: new targets.LambdaInvoke(props.func, {
        ...targetBaseProps,
        // override whatever or not to override
        }),
    }),
});

Description of changes

Removed targetOverrides prop and the related tests. Also updated the integ test which was using the prop.

Description of how you validated changes

Removing a prop so n/a.

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

BREAKING CHANGE: This PR removes the targetOverrides prop from the Schedule construct.