fix: fixed an issue causing lambda package to hang in CI/CD

[philasmar]

Description of changes:

• Applied a workaround for the hanging dotnet publish process which hangs on Process.WaitForExit() because of a dotnet tooling bug. There are issues on Microsoft's repos such as this one Process.WaitForExit() deadlocks when waiting on "dotnet.exe build /m /nr:true" dotnet/msbuild#2981. The suggested workaround is to add a very large timeout which solves the issue. I have tested it in our pipelines and the tests ran blazingly fast.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[normj]

Copying a side conversation. I think we need to better understand the hanging before making this change. The latest version of this tool is pulled into a lot of CI builds so we need to be really careful. Also I don't like that the new user experience wouldn't show any output till the dotnet command is complete. For a big project that could take awhile for the build to complete and see the output.

[philasmar]

Copying a side conversation. I think we need to better understand the hanging before making this change. The latest version of this tool is pulled into a lot of CI builds so we need to be really careful. Also I don't like that the new user experience wouldn't show any output till the dotnet command is complete. For a big project that could take awhile for the build to complete and see the output.

I changed the approach to a workaround suggested in dotnet/msbuild#2981.

[Kuinox]

I don't know your use case but the danger of this workaround is getting a truncated stdout/stderr.