Align security scope with guideline

[bigludo7]

Problem description
As described in recent merged PR177 in commonalities we have to update the security part, openId defined scope in geofencing-subscriptions yaml.

for GET we must have:

Expected behaviorcamaraproject/Commonalities#177

For GET & GET {id} we must have

security:
        - openId:
              - geofencing-subscriptions:read

for DELETE:

security:
        - openId:
              - geofencing-subscriptions:delete

For POST

security:
        - openId:
              - geofencing-subscriptions:org.camaraproject.geofencing.v0.area-entered:create
              - geofencing-subscriptions:org.camaraproject.geofencing.v0.area-left:create

Alternative solution

Additional context
@maxl2287 probably for you as you maintain this yaml ;)

[jlurien]

@bigludo7, if API is renamed to geofencing-subscriptions, should we have to rename as well events to org.camaraproject.geofencing-subscriptions.v0.area-...?