Allow definition of multiple partition strategies in the Avro schema

If we want to allow persisting of records of an avro schema to multiple tables that have different key structures, we need to allow keys to be defined per table instead of through mapping annotations like they are done today. While doing this, we should support the entire array of field partitioners instead of just one id field partitioner per key field.