Improve verifications to verify rollout deployments

[ViliusS]

This PR uses the same algorithm as "kubectl rollout status" for the verification of rollout deployments.

Fixes #119

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[ViliusS]

@olamy ping

[ViliusS]

@basil can this be merged? The plugin seems to be abandoned by Google, but it is still useful.

[basil]

Hi @ViliusS, I'm not doing feature work on this plugin, but you can adopt it following the instructions at https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/

[ViliusS]

@olamy @craigdbarber @stephenashank @donmccasland @batmat @raul-arabaolaza is anyone still maintaining this plugin, o was it abandoned?

[Copilot]

Pull Request Overview

This PR improves the verification process for rollout deployments by aligning the logic with the kubectl rollout status algorithm. Key changes include updating test assertions to reflect new replica terminology, modifying the log message to use a pre-defined message constant, and revising the deployment verification logic to compare available, updated, and desired replicas.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/test/java/com/google/jenkins/plugins/k8sengine/KubernetesVerifiersTest.java	Updated test assertions and renamed variables to match the new verification logic
src/main/java/com/google/jenkins/plugins/k8sengine/VerificationTask.java	Updated the log message format to use a message constant for consistency
src/main/java/com/google/jenkins/plugins/k8sengine/KubernetesVerifiers.java	Revised the deployment verification logic and updated related JSON paths and constants

Comments suppressed due to low confidence (1)

src/main/java/com/google/jenkins/plugins/k8sengine/KubernetesVerifiers.java:175

• Adding an inline comment to explain the rationale behind these specific replica comparisons (and how they mirror the kubectl rollout status behavior) would improve code clarity and maintainability.

                    && availableReplicas.intValue() == updatedReplicas.intValue();