Follow-up changes based on #3768

[gautamguptabasant]

Dear Gobblin maintainers,

Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!

JIRA

• My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
  • https://issues.apache.org/jira/browse/GOBBLIN-XXX

Description

• Addressing comments on the PR [GOBBLIN-1904] Refactoring SalesforceSource class for better code organization and testability #3768
• The changes in this PR are around organization of the code only. There are no functional changes.

Tests

• No change in functionality - no new tests added.

Commits

• My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

[phet]

thanks for the follow up!

(looks good, so long as nothing warranted by the comment I raised)

[phet]

maybe add comment on why another getConnector(state), rather than reusing

edit: reading on I see it doesn't create a new connector... just looks that way

[phet]

this is not thread-safe... should it be synchronized? (if there's any need to explicitly close the connector, there's a potential resource leak.)