feat: Added weighted-forward rules for HTTP

[gbloquel]

Description

This PR add 'weighted-forward' dynamic action block to use with the http_tcp_listener_rule for multiple weighted target_group.
It is very close to #224 but manage the http.

Motivation and Context

This adds a dynamic action block for a "weighted-forward" action_rule.type for the http_tcp_listener_rules . It allows us to create a listener rule like:

{
  http_tcp_listener_index = 0
  priority                = 30

  actions = [
    {
      type = "weighted-forward"
      target_groups = [
        {
          target_group_index = 1
          weight             = 1
        },
        {
          target_group_index = 0
          weight             = 0
        }
      ]
    }
  ]

  conditions = [{}]
}

Breaking Changes

No breaking changes

How Has This Been Tested?

• I have tested and validated these changes using one or more of the provided examples/* projects

I created the resources and visually verified the correct rules made it onto the load balancer.

+ forward {
  + stickiness {
    + duration = 0
    + enabled  = false
  }
  
  + target_group {
    + arn    = "arn:aws:elasticloadbalancing:eu-west-1:../21b716c2bd84930d"
    + weight = 1
  }
  + target_group {
    + arn    = "arn:aws:elasticloadbalancing:eu-west-1:../6c33705a9ab0897a"
    + weight = 2
  }
}

[gbloquel]

Also complete fixes #211

[gbloquel]

Hello @antonbabenko
Could you review my PR ?
Regards,

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[gbloquel]

Hello @antonbabenko
Could you review my PR ?
Regards,

[antonbabenko]

This PR is included in version 6.9.0 🎉

[antonbabenko]

Thank you @gbloquel !

Sorry that it took some time for this to be merged.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.