Add aborted feature at change level for post change validations

What does this MR do and why?

Add the aborted logic so if we want to abort the change after some post processing in each_change method we can do that. An example use case can be we built the changes to remove the feature_flag but after searching the codebase we still find the references then we can abort the change.

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

• !147206

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #450442

added Engineering Productivity automation:ml automation:ml wrong groupglobal search sectioncore platform labels

assigned to @sdungarwal

added pipelinetier-1 label

@DylanGriffith can you do an initial review and assign to @dgruzd or someone else who is actively contributing to the housekeeper project.

requested review from @DylanGriffith

added backend label

	2 Warnings
⚠️	featureaddition and featureenhancement merge requests normally have a documentation change. Consider adding a documentation update or confirming the documentation plan with the Technical Writer counterpart. For more information, see: The Handbook page on merge request types. The definition of done documentation.
⚠️	This merge request does not refer to an existing milestone.

	1 Message
📖	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
backend	@olaoluro (UTC+0, 5.5 hours behind author)	@lma-git (UTC-8, 13.5 hours behind author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the 🔁 danger-review job that generated this comment.

Generated by 🚫 Danger

Proper labels assigned to this merge request. Please ignore me.

👋 @sdungarwal - please see the following guidance and update this merge request.

	1 Error
❌	Please add typebug typefeature, or typemaintenance label to this merge request.

added featureenhancement typefeature labels

resolved all threads

added featureaddition label and removed featureenhancement label

approved this merge request

added pipeline:mr-approved label

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you set this MR to auto-merge, please check the following:

• You are the last maintainer of this merge request
• The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
• This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

enabled automatic add to merge train when checks pass

Thanks for extracting this @sdungarwal ! Looks good.

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-cng: ✅ test report for 53ca0e47

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Create      | 140    | 0      | 22      | 0     | 162   | ✅     |
| Fulfillment | 2      | 0      | 7       | 0     | 9     | ✅     |
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Verify      | 52     | 0      | 20      | 0     | 72    | ✅     |
| Plan        | 86     | 0      | 8       | 0     | 94    | ✅     |
| Govern      | 84     | 0      | 10      | 0     | 94    | ✅     |
| Package     | 29     | 0      | 15      | 0     | 44    | ✅     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| Secure      | 2      | 0      | 5       | 0     | 7     | ✅     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 444    | 0      | 127     | 0     | 571   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

e2e-test-on-gdk: ✅ test report for 53ca0e47

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Package     | 24     | 0      | 14      | 0     | 38    | ✅     |
| Govern      | 79     | 0      | 13      | 0     | 92    | ✅     |
| Create      | 135    | 0      | 23      | 0     | 158   | ✅     |
| Plan        | 82     | 0      | 8       | 0     | 90    | ✅     |
| Verify      | 51     | 0      | 21      | 0     | 72    | ✅     |
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Secure      | 4      | 0      | 3       | 0     | 7     | ✅     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Fulfillment | 2      | 0      | 7       | 0     | 9     | ✅     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 426    | 0      | 129     | 0     | 555   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

added this merge request to the merge train at position 2

merged

mentioned in commit 53c97cca

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

changed milestone to %17.9

added workflowpost-deploy-db-staging label and removed workflowproduction label

added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label

added releasedpublished label