refactor(httpReceiver): rename module http-receiver to transfer-pull-http-receiver

[wolf4ood]

…

What this PR changes/adds

Rename module http-receiver to transfer-pull-http-receiver

Why it does that

comprehensiveness

Further notes

While renaming I've added a test on HttpEndpointDataReferenceReceiver

Linked Issue(s)

Closes #2229

Checklist

• added appropriate tests?
• performed checkstyle check locally?
• added/updated copyright headers?
• documented public classes/methods?
• added/updated relevant documentation?
• assigned appropriate label? (exclude from changelog with label no-changelog)
• formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

[ndr-brt]

Since with the last PR by @bscholtes1A we better shaped the terminology for transfer types as "consumer pull" and "provider push", I'd propose to switch sync with pull, to keep an uniform terminology. wdyt?

[bscholtes1A]

I would still keep the term http in the extension name, as this is one possible type of receiver but we might have other not relying on http, e.g. a receiver putting the EDR into a Vault...

[wolf4ood]

@bscholtes1A transfer-pull-http-receiver ?

[ndr-brt]

another proposal, since there's also the transfer-data-plane, a transfer folder containing both the extension could make everything tidier

[wolf4ood]

@ndr-brt make sense, will do