Separation of embedding layer and pooling needed

[Alicegaz]

There is a package pooling which stores everything that can be used independently to process output feature maps coming from backbone. However, embedding layers can utilize different poolings and I suggest the following hierarchy:

backbones
emb_layers
heads
modules
    blocks
    bricks
    layers
        activations
        normalizations
        poolings
    necks

Top level contains components that are used in a task, here embedding_layer should replace POOLINGS.

[PososikTeam]

You can write your own POOLING class with different poolings. For example you need Average Pooling with Linear layer, so we wrote PoolingLinear that exactly do this. So the thing what you suggest it is just renaming POOLING to EMB_LAYER.