feat: support for composite/sub partitioning

[quertenmont]

Hello,

I needed to have composite partitioning (aka nested or subpartitioning),
I made the changes to make it work for one level subpartitioning.

The principal changes are:

1. Handling "submethod" and "subkey" variable in the partitioning meta object
2. Adding partition_by and parent_partition_name in the PostgresPartition class to make it aware that it could have either parent or child partition (and add the PARTITION OF and PARTITION BY sql statement where needed)
3. Adding a submethod in the Config to handle how the second level should be created
4. Updating the manager to create a second level of partition if needed

I tested the code with TimePartitioning at first level and a List partitioning at second level, it's working nicely.

The code could certainly be improved, but the functionality is there and it would certainly be useful to others to have it in the main package. Thanks for considering its inclusion.

[Photonios]

Thanks for giving it a shot!

There are some items that prevent me from considering inclusions at this time:

1. PR re-formats unrelated code.
2. Lack of unit tests.
3. Left-over prints and debugging code.

I am happy to leave the PR open for the time being so it can be improved or to serve as inspiration for others wishing to do the same.

[Photonios]

Why is this here?

[quertenmont]

that could actually be removed.
I added that to print sql statement and debug my code implementation.

[quertenmont]

Yes, the main goal of the PR was to give it over to someone else to polish and commission the code for inclusion :-)

I don't have much time nor patience to do it myself :-)