Fix FeatureSetJobStatus removal

[pyalex]

What this PR does / why we need it:

Currently due to cascade relations from both Job and FeatureSet to FeatureSetJobStatus it's impossible to delete FeatureSetJobStatus. As a solution I propose to delete cascade on FeatureSet side because:

1. We manage FeatureSetJobStatus from Job side
2. Ideally when we completely decouple JobCoordination from Core there will be no foreign key (relationship in general) to FeatureSet in FeatureSetJobStatus (see my other PR Keep StoreProto inside JobStore to decouple JobCoordination from SpecService internals #852 )
3. Currently we not planning to physically delete feature sets. Even if we will delete them - only by marking as deleted.

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pyalex

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [pyalex]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mrzzy]

Its not clear what problem this solves. @pyalex mind updating PR description?
Removing the cascade entirely does not seem intuitive: deleting a FeatureSet should also clean up its corresponding FeatureSetJobStatus? Is this is already enforced by the feature_set_id foreign key constraint on FeatureSetJobStatus?

[pyalex]

@mrzzy updated PR description

[woop]

Ok makes sense. Deletion is hard. It will cause inconsistency here. Lets assume feature sets dont get deleted completely but only marked as deleted.

[woop]

/lgtm

[pyalex]

/test test-end-to-end-auth