Remove deprecated bindings for release

[eisenhauer]

No description provided.

[eisenhauer]

@pnorbert I think we had a conversation about this last year, but I don't remember what forum (email, git, slack, etc.). However, I think this is the gist of it: At least some of the contracts tests failing here are pulling source from external repos to see if they will still compile after the commit. Those that still rely upon deprecated APIs will not compile after we remove said APIs. Some of those externals, like the adios examples, we can fix ourselves. Others require getting fixes pushed into repos of our collaborators. We probably should have been pushing to get that done as soon as we marked some things deprecated. We did not. But if we want to kill deprecated things as part of this release, we do need to sort this somehow.

[anagainaru]

Not sure they are relevant but there are some references to the debug mode in some examples/testing codes and in the documentation.

Otherwise it looks good to me.

[eisenhauer]

Not sure they are relevant but there are some references to the debug mode in some examples/testing codes and in the documentation.

I grep'd for "debug" in the rest of the stuff, but maybe I missed things. If you have pointers, please share!

[anagainaru]

I double checked and even though the comments refer to using debug mode, the code doesn't actually do it. Your changes are the only ones I could find as well. Your code passes the tests on my laptop.

[vicentebolea]

CI shows builds errors errors due to calls in some parts of the code to those newly deleted functions.

[eisenhauer]

CI shows builds errors errors due to calls in some parts of the code to those newly deleted functions.

Anything other than what I reference in the first note above?

[vicentebolea]

CI shows builds errors errors due to calls in some parts of the code to those newly deleted functions.

Anything other than what I reference in the first note above?

Nope, it looks good to me :)