[FIX]: delay the initialization of fields keyStore, trustManager, and sslContext

[Vandit1604]

See JENKINS-70206.

Testing done

Proposed changelog entries

delay the initialization of fields keyStore, trustManager, and sslContext until and unless getName() is initialized

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.

Maintainer checklist

Before the changes are marked as ready-for-merge:

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[basil]

Closing in favor of #7514.