Add support for BitFieldSubCommands that generate multiple bit operations using non-chaining methods

[Yanam]

resolves #2055

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

[mp911de]

Instead of uncontrolled opening up the API, we should rather introduce factory methods with proper assertions, something like:

BitFieldGet.create(…)

that can be later on used with BitFieldSubCommands through a BitFieldSubCommands.create(BitFieldSubCommand…) and BitFieldSubCommands.create(Iterable<? extends BitFieldSubCommand>).

[Yanam]

Instead of uncontrolled opening up the API, we should rather introduce factory methods with proper assertions, something like:

BitFieldGet.create(…)

that can be later on used with BitFieldSubCommands through a BitFieldSubCommands.create(BitFieldSubCommand…) and BitFieldSubCommands.create(Iterable<? extends BitFieldSubCommand>).

Thanks for the suggestion, I hadn't thought about it before, I'll submit a new pull later to improve it

[mp911de]

Feel free to either push additional commits onto your branch or force-push an amended commit. GitHub Pull requests automatically pick up your changes, so no need to create a new pull request.

[mp911de]

Thank you for your contribution. That's merged, polished, and backported now.