[GOBBLIN-1220] Log improvement

[arjun4084346]

Dear Gobblin maintainers,

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

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-1220

Description

• Here are some details about my PR, including screenshots (if applicable):
  a) this pr fixes some minor typos, whose impact might not be very ignorable.
  b) add toString GaaS Node class to improve log
  c) reduce helix job initialization time from Long.MAX_VAL to 5 minutes
  d) increase time between two helix job status checks from 1 second to 10 seconds to reduce logs

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:
  trivial changes

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"

[autumnust]

why removing?

[arjun4084346]

It was being called only from two places, with fix value in both the places , one is "300_000" (which has a typo), other is Long.MAX_VALUE, which doesn't make sense. I think we should not try that much for a helix job to initialize. I have fixed it to 5 minutes.