[FLINK-11544] Add jobId to JarRequestBody

[uce]

What is the purpose of the change

• This PR adds the optional jobId entry to JarRequestBody
  • If specified, users manually set the job ID of a job when submitting a JAr
  • If not specified, we keep the current behavior

Brief change log

• Add jobId to JarRequestBody
• Parse jobId when generating JobGraph

Verifying this change

• This change added unit tests for added functionality
• If you want to manually verify this change, you can follow these steps:
  1. Build this branch
  2. Upload examples/streaming/TopSpeedWindowing.jar via web UI
  3. Get $jarId from /v1/jars endpoint
  4. Execute curl -X POST -d '{}' http://localhost:8081/v1/jars/$jarId/run (expected: random job ID)
  5. Execute curl -X POST -d '{"jobId": "4\. fd72014d4c864993a2e5a9287b4a9c5d"}' http://localhost:8081/v1/jars/$jarId/run (expected: job ID fd72014d4c864993a2e5a9287b4a9c5d)

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): yes (adds new field in request body of a v1 REST API endpoint)
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: no
• The S3 file system connector: no

Documentation

• I didn't add any documentation as I assume that the REST API docs are auto generated (@zentol please correct me if I'm wrong)

[uce]

CC @yanghua @zentol

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Review Progress

• ❌ 1. The [description] looks good.
• ❌ 2. There is [consensus] that the contribution should go into to Flink.
• ❔ 3. Needs [attention] from.
• ❌ 4. The change fits into the overall [architecture].
• ❌ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve the 1st aspect (similarly, it also supports the consensus, architecture and quality keywords)
• @flinkbot approve all to approve all aspects
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval

[zentol]

Please regenerate the rest api docs, apart from that +1.
@flinkbot approve all

[uce]

@zentol Thanks for the review. I rebased on master, regenerated the docs, and I am now waiting for Travis to complete before merging this.

[zentol]

When merging, please update the commit component tag to [rest]

[rmetzger]

I will merge this PR