Add support for producing EnhancedType with tableSchema from Sets

[jaredwindover]

Motivation and Context

There's support for Sets in DefaultAttributeConverterProvider, but it was missing from BeanTableSchema. As a result, Sets always require a customer converter, but Lists do not. This adds support for Set in BeanTableSchema.

Modifications

I added a stanza in BeanTableSchema::convertTypeToEnhancedType that checks if the type is a Set, and handles it analogously to how lists and maps are being handled. I also added a test modelled on the existing tests for list and map.

Testing

I couldn't get the project building locally, so I haven't tested it.

Screenshots (if appropriate)

Types of changes

I don't know which of these it is. It seems like a bug, since there is support for Set half implemented, but it's not documented anywhere.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license