feat: return 200 (not 204) for PUT requests to entity verticles

[dapeng-wang]

No description provided.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[pk-work]

In the last NeonBee Committer Meeting we discussed this PR with @kristian . We came to the following conclusion:

-> Responds with a Location Header / Hint, use Location as returned by EntityVerticle
-> Responds with a Entity that defines the primary key completely then generate relative location header in ODataEndpoint, e.g. EntitySetName(PrimaryKey) (check if helper method in Olingo is available)
-> Responds without a entity (e.g. empty future) or the returned entity does not contain the full primary key, continue as of now and NOT set the location header
-> In future, to be able to use absolute URLs in Location header instead: provide helper method in NeonBee to generate absolute header based on currently RoutingContext and also add new „absoluteURLPrefix“ configuration (e.g. /backend as this is added by AppRouter not NeonBee)

[s4heid]

Only found the two typos in the doc. Implementation looks good to me :)

I created #374 to tackle the leftovers of Pascals comment. As agreed in the last committer meeting, we split the implementation.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication