fix(terraform): update less-than/less-than/equals version constraints

[bryan-bar]

Issue:
When using the terraform dependency constraints less-than or less-than/equals to set a max version, only the largest semvar version number is updated. This allows the provider version to be set to a non-existent version.

example:
Latest provider version: 0.7.0
Provider version suggested changed: 0.6.1 -> 0.7.1

fixes #8959

---

Fix:
Update each version index to tighten the constraints:

• less-than/equals allows provider versions up to the latest version or latest requirement
• less-than allows for a provider version up the latest minus 1 against the smallest defined semvar number.

[bryan-bar]

Hello @caspermeijn @bdragon @sachin-sandhu,

If I could get a reviewer set on this PR or comments on how to move forward with this fix please.

It is similar to the versioning issue with cargo in #9828

[abdulapopoola]

Thanks @bryan-bar , can you please resolve the conflicts and we can get this merged. Thanks for fixing this.

[caspermeijn]

I believe the original implementation of update_greatest_version was correct for "<" requirements, but "<=" requirements need to be handles differently.

This is what I did for cargo:

dependabot-core/cargo/lib/dependabot/cargo/update_checker/requirements_updater.rb

Lines 134 to 147 in 4f2cfb5

	def update_range_requirements(string_reqs)
	string_reqs.map do |req|
	next req unless req.match?(/[<>]/)
	ruby_req = Cargo::Requirement.new(req)
	next req if ruby_req.satisfied_by?(target_version)
	raise UnfixableRequirement if req.start_with?(">")
	req.sub(VERSION_REGEX) do |old_version|
	if req.start_with?("<=")
	update_version_string(old_version)
	else
	update_greatest_version(old_version, target_version)

I think you need to focus on update_range for handling "<" and "<=" differently.

[bryan-bar]

@caspermeijn
The less-than operator should still be incremented. I updated the PR to handle both < and <=.

The issue with the function is that < also returned an inconsistent version so I chose to update it.
For example, < 0.3.0 with a latest version of 0.3.7 would return as < 0.4.0
Change the initial version to < 0.3.2 with a latest version of 0.3.7 and the returned version changed to < 0.3.8

It seems index_to_update is setting the wrong index to be incremented and then anything after is set to 0 or skipped over.

Another issue is that terraform does not have wild cards and it also did not expand the version when it has less than 3 segments like it does for some of cargos operators.
For less-than/equals, that would mean incrementing the version and then restricting it (example assuming current version <= 1.6, new version 1.6.5 -> <=1.7, !=1.7) or expanding the version as is ( <= 1.6.5). Another option would be to set a really high version <= 1.6.9999 or converting it to less than < 1.7.

[bryan-bar]

@caspermeijn @abdulapopoola
Also note that Terraform treats non-semantic versions as being expanded out internally. 0.2 == 0.2.0 | 1 == 1.0.0
I added this comment in the code as well.

[Zawadidone]

@bryan-bar are you working on this PR?

[bryan-bar]

@bryan-bar are you working on this PR?

Yes, thanks for the reminder. I just updated the PR.