Replace all Supplier/Consumer Pairs with Functions

## What shortcoming will this fix cover
Currently Jetedge uses Supplier/Consumer Pairings in order to generate Pojos. To create a more robust backend, it would be better for these pairings to be replaced with function pairs in order to allow for more flexible deliveries.

## Why its important to make this change
This change will be required for the scratcher interface to be built and, in the future, a coorelation limiter across two different Pojo Generators.

## How much time I would invest in making this patch (if I had the free time to do it)
10 hours

The issue names Supplier/Consumer pairings used to generate POJOs but does not identify files or tests. Trace those pairings through the POJO generator entry points first, then determine the scope of replacing them with function pairs and verify that generation still works while supporting the planned scratcher interface.

Written by the indexing model from the issue text.