+1 unless above test failures are because of this patch.
A natural extension of this is to move Noop TableFunctionEvaluator to contrib/ module and then do create function for it in tests where it is used. Currently, Noop lives in main src tree because of this bug but used heavily in tests. Since contrib/ jar is not on classpath of tests by default, having this test-used class live in contrib/ will help in both regards, keeping src tree free of any test classes and provide true test case for this functionality, since current test uses function which any way is available in classpath of tests.
Since above may require some refactoring, I am OK with doing that in a follow-up jira.