Remove the hardcode 0 and use the default value for LauncherExecutor (#…

…3153)

The original hardcode 0 has a problem, if the external user code has an
exception and the program will never return.
Our FL client job process (running LauncherExecutor) will never ends.
By using the default heartbeat_timeout value, if the FL client job
process does not receive the heartbeat from the user process for
heartbeat_timeout seconds, then we will consider it dead.

### Description

- Remove the hardcode 0 and use the default value for LauncherExecutor

### Types of changes
<!--- Put an `x` in all the boxes that apply, and remove the not
applicable items -->
- [x] Non-breaking change (fix or new feature that would not break
existing functionality).
- [ ] Breaking change (fix or new feature that would cause existing
functionality to change).
- [ ] New tests added to cover the changes.
- [ ] Quick tests passed locally by running `./runtest.sh`.
- [ ] In-line docstrings updated.
- [ ] Documentation updated.

nvflare/job_config/script_runner.py

@@ -207,7 +207,6 @@ def add_to_fed_job(self, job: FedJob, ctx, **kwargs):
                     params_transfer_type=self._params_transfer_type,
                     from_nvflare_converter_id=self._from_nvflare_converter_id,
                     to_nvflare_converter_id=self._to_nvflare_converter_id,
-                    heartbeat_timeout=0,
                 )
             )
             job.add_executor(executor, tasks=tasks, ctx=ctx)