Upgrade Terraform version to 1.5.x for WLS for OCI

[rachavan]

Upgrade Terraform version to 1.5.x for WLS for OCI.

Testing done - Stack provisioning successful through ORM with Terraform version 1.5.7.

[oracle-contributor-agreement]

Thank you for your pull request and welcome to our community! To contribute, please sign the Oracle Contributor Agreement (OCA).
The following contributors of this PR have not signed the OCA:

• PR author: rachavan
• rachavan@rajeshs-macbook-pro.local

To sign the OCA, please create an Oracle account and sign the OCA in Oracle's Contributor Agreement Application.

When signing the OCA, please provide your GitHub username. After signing the OCA and getting an OCA approval from Oracle, this PR will be automatically updated.

If you are an Oracle employee, please make sure that you are a member of the main Oracle GitHub organization, and your membership in this organization is public.

[telake]

I can see from code changes that load balancer was changed, but I don't know all the code paths that were tested. secured production mode, mount targets, file system, autoscaling, existing ORM, OMH profile?

[rachavan]

I can see from code changes that load balancer was changed, but I don't know all the code paths that were tested. secured production mode, mount targets, file system, autoscaling, existing ORM, OMH profile?

I have tested with new and existing load balancer. I will test the configurations mentioned above and update the result in the PR

[rachavan]

I can see from code changes that load balancer was changed, but I don't know all the code paths that were tested. secured production mode, mount targets, file system, autoscaling, existing ORM, OMH profile?

I have tested with new and existing load balancer. I will test the configurations mentioned above and update the result in the PR

@telake The change to load balancer code w.r.t terraform v1.5 only affect a case when user chooses to create a new load balancer. This scenario is already tested.
Apart from this, I have tested provisioning though ORM with secure & non-secure production modes, existing ORM, OMH profile, with JRF (v12.2.1.4 with Database system) and non-JRF (v14.1.1).

[telake]

Let's test autoscaling since that creates a bunch of other OCI resources, but that doesn't prevent approving these changes.