extend destination factory to allow for custom names and config sections

[rudolfix]

Background
With #746 destinations can be used like sources (imported and then parametrized). Here we add more flexibility on how to configure them,

*Tasks

1. • in DestinationClientConfiguration rename destination_name to destination_type: it is a Final (non configurable) field (we can convert it into class var as well)
2. • add name field which defaults to destination_type if not provided.
3. • use the ability of with_config to accept section as lambda that takes the arguments of the function to generate dynamic config section for a destination: [destination.<name>], please fix with_config signature and add unit test for it
4. • add environment (str) config field with default None
5. • each destination factory must accept the base fields of DestinationClientConfiguration (name, environment, credentials) and expose them as attributes

Implementation
This probably impacts #746 - we should get rid of current destination reference and most of the init of implementation in favor of destination factory.

relevant part of with_config that deals with dynamic sections

# if section derivation function was provided then call it
                if section_f:
                    curr_sections: Tuple[str, ...] = (section_f(bound_args.arguments), )
                    # sections may be a string
                elif isinstance(sections, str):
                    curr_sections = (sections,)
                else:
                    curr_sections = sections