feat: return handleCommitRequest early if already hydrated

[jcy0308]

close #19592
Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[nitishfy]

Suggested change

	if err == nil {
	if err != nil {
	// handle the error
	}
	var hydratorMetadata hydratorMetadataFile
	json.Unmarshal(fileData, &hydratorMetadata)
	if hydratorMetadata.DrySHA == r.DrySha {
	logCtx.Debug("Already Hydrated")
	return "", r.DrySha, nil
	}

Minor but this way we are handling the error too if received when trying to read the file..

[nitishfy]

A minor comment but overall looks good!