split /subscription-endpoints into seperate APIs

[maxl2287]

What type of PR is this?

Add one of the following kinds:

• enhancement/feature
• cleanup

What this PR does / why we need it:

Splits up the subscription-endpoints for reachability and roaming status into seperate YAML-files.

Which issue(s) this PR fixes:

Fixes #125

[bigludo7]

Thanks @maxl2287 for the effort.
I guess we have to align with the new model for subscription.
Do we handle this in this PR or in a separate one?
cc: @akoshunyadi

[maxl2287]

@bigludo7 tbh I would handle this in a seperate PR 😄

Do you both agree?

[bigludo7]

@bigludo7 tbh I would handle this in a seperate PR 😄

Do you both agree?

Works for me.
It means that we have to merge this one quickly in order to no block you to move forward with this newt PR - Correct?

[akoshunyadi]

ok for me. Yes, then then we need an additional PR for the subscriptions.

[bigludo7]

OK for me in order to move forward to the new model.

[maxl2287]

@sachinvodafone thanks for the findings!

[bigludo7]

OK for me

[maxl2287]

@bigludo7 can we label this as v0.6.0 ?
(I am not allowed to 🥲 )

[akoshunyadi]

Just some typos... the big rework based on the new template will come anyway..

[bigludo7]

LGTM

[maxl2287]

@bigludo7 I was needed to update the file-name to device-reachability-status-subscriptions.yaml

Please review again :)

[bigludo7]

We need to align with PR213 outcomes for the error linked to the device identifier but in order to not manage too complex PR I will prefer to merge this one and then raise another issue/PR to manage 213.
@maxl2287 @akoshunyadi @sachinvodafone WDYT?

[akoshunyadi]

Actually the scope should be api-name:[resource:]action, so in this case device-reachabilty-status-subscriptions:create
(applies to other scopes in this PR too)

[akoshunyadi]

@maxl2287 we can also merge this PR as it is since #162 needs to be done anyway, which will rework it, right?