1197: prepare beta-10.4 release

[cz4rs]

fixes #1197

[PhilMiller]

Tested successfully in EMPIRE with gcc. Nvidia and Intel are pending.

[PhilMiller]

Intel tests pass. Testing on CUDA is slow.

[cz4rs]

@PhilMiller
Codacy and Travis jobs are stuck, other tests pass fine. As with the other PR, I cannot merge it myself (no permissions for override + I think merging into 1.0.0 is restricted as well)

if everything is ok, can you please merge this? (I will create the tag afterwards)

[cz4rs]

Regarding the extended tests, I have added the build definitions, but it seems like they have not been triggered.

Honestly I don't know if there should be much investigation put into this, since extended tests are failing regularly on develop anyways (I believe this was discussed at the last DARMA weekly, but there's no solution so far)

[PhilMiller]

We're looking at incorporating

• 914 Fix stacktrace symbols when dladdr fails #915 Stacktrace generation
• A fix for missing deletion of https://github.com/DARMA-tasking/vt/pull/1113/files#diff-51dbee743b2faddab4d156c0fbf6707273c54f18e7b48a53480eefb455e0e2f0L100 in the backport onto beta 10.3 (1111 Fix for large message sends #1113 / Merge 1.0.0 beta.10.3 proposed update into 1.0.0 #1187)
• 1098 Enable assertions during CI when release builds are used #1107 assertions in CI builds

[cz4rs]

note: #1098 has 2 PRs, but they were both done on 1098-enable-assertions-during-ci branch

[PhilMiller]

This passes the full EMPIRE test suite in the Debug mode builds that unexpectedly failed. I'm re-running the test in other modes to not repeat my earlier mess.

[PhilMiller]

Manual and automatic testing of Release mode EMPIRE builds also passes. I'm re-running Intel 19 tests as well

[PhilMiller]

Intel 19 tests all pass as well. I think this is good to go.

[cz4rs]

Intel 19 tests all pass as well. I think this is good to go.

👍

@PhilMiller @lifflander
If the CMake conversation above can be resolved as a non-issue, please merge this PR (I cannot do this myself - this is targeting release branch + Codacy is stuck again). I will create a tag & release notes afterwards.

edit: I'm not even sure about Codacy, because it is displayed twice with different statuses for me
regarding Travis - I have no idea why it shows up (the configuration file was removed long time ago)

[lifflander]

I think Travis CI needs to be removed for merging on release. I've changed the requirements.

[lifflander]

Looks good to me. Let's merge.