[GOBBLIN-2200]Moving Away From Azkaban Execution Id

[pratapaditya04]

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

Description

• Here are some details about my PR, including screenshots (if applicable):
  Moving Away From Azkaban Execution Id
  In several places we use azkaban.flow.exec.id config values to identify the jobExecution, since we don't want to tie Gobblin to Azkaban, introducing a new field gaas.job.execid which will serve as the configuration Key for a unique job execution identifier in GaaS, the value is a UUID
  Have also added gaas.job.execid.hash to be used for jobExecutionId for backwards compatibility, as jobExecutionId is Long and is used in several places and also in GTE events

Tests

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

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"