Adding min version requirements for flex consumption

[soninaren]

Issue describing the changes in this PR

Enforcing extension bundle v4 as minimum required version for flex consumption SKU. Using bundle version 4.12.0 as minimum required version as that is the earliest version that is currently used in flex consumption. Also this is the first extension bundle that includes durable version 2.12.0, that has some necessary updates for Flex consumption.

resolves #9478

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

• Backporting to the in-proc branch is not required
  • Otherwise: Link to backporting PR
• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR - Update the documentation include minimum extension versions enforcement for Flex consumption Azure-Functions#2512
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

[fabiocav]

I realize the PR and linked issue mention Flex, but we should avoid SKU specific logic for this. As long as there is a mechanism that enables the environment to configure the rules, the implementation would be SKU agnostic.

[pragnagopa]

gentle bump on this to prioritize completion to help with FlexConsumption deployment schedules

Addressed feedback already