Reinstate "Optimize issuable updates"

What does this MR do?

This reinstates !58114 (merged), which was reverted in !59355 (merged) due to causing a master:broken in #327668 (closed).

The fix for the failing spec was removing the unneeded stub_const usage in !59359 (merged).

The specs still pass in this MR when run in the order that was previously triggering the problem:

bin/rspec ee/spec/features/epics/epic_issues_spec.rb ee/spec/services/ee/issuable/bulk_update_service_spec.rb
bin/rspec ee/spec/services/epic_links/create_service_spec.rb ee/spec/services/ee/issuable/bulk_update_service_spec.rb

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team

Related to #21068