Feat Cross App CallActivity

[cicoyle]

Add support for cross app call activity calls.

[cicoyle]

Note, this PR should be cherrypicked into the release branch once merged.

[cicoyle]

This PR is also dependent on the dapr release for 1.16. Javi has a PR to update to the latest rc version here. We will need both merged in, then cherrypick both to the release branch

[cicoyle]

I need to release durabletask-java with this PR merged in before this current PR will be green

[salaboy]

@cicoyle I was looking at this PR, but it doesn't have anything related to cross app call activity.

[cicoyle]

@cicoyle I was looking at this PR, but it doesn't have anything related to cross app call activity.

Did you by chance read the thorough readme updates I added?

[cicoyle]

I just got a workflow IT test locally 🎉 Need to cleanup and push, will do that + fix the conflict in my morning. Please feel free to review everything else and know I will update the pom.xml in my morning and add an IT test. Ill remove the mechanical markdown since Ill be adding the IT test.

[salaboy]

@cicoyle I've left a bunch of comments and suggestions. I am really against adding support for customHttp and customGrpc ports that is something that users shouldn't need to do as that goes against the idea of using containers that are started with random ports, but still allow the user to obtain the mapped ports to connect to them.

[salaboy]

@cicoyle here you can use the Testcontainers mapped (random) port instead of relying on a custom port number.

[salaboy]

@cicoyle overall the example looks good and the new additions for Cross App Call are good, but I believe that all the changes in the DaprContainer class will cause issues. I am curious to see what are the issues that you are facing if you don't introduce any change in that class.

DaprContainer is a critical class being used by customers now, so I would change the behavior of it.

My recommendation would be to revert the changes on DaprContainer and I can help you to figure out what is going wrong with the containers when the pipelines fail.

[codecov]

Codecov Report

❌ Patch coverage is 75.00000% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 78.68%. Comparing base (d759c53) to head (c21016e).
⚠️ Report is 200 commits behind head on master.

Files with missing lines	Patch %	Lines
...in/java/io/dapr/workflows/WorkflowTaskOptions.java	66.66%	5 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1468      +/-   ##
============================================
+ Coverage     76.91%   78.68%   +1.77%     
- Complexity     1592     1921     +329     
============================================
  Files           145      237      +92     
  Lines          4843     5940    +1097     
  Branches        562      610      +48     
============================================
+ Hits           3725     4674     +949     
- Misses          821      944     +123     
- Partials        297      322      +25     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.