Remove unused config container under /system/alarms mislabeled as config=false

[earies]

• (M) release/models/system/openconfig-alarms.yang
  • Remove config container and retain entire hierarchy for alarms as
    read-only

Change Scope

The current published /system/alarms hierarchy is tagged as read-only however
a config container grouping was introduced to follow common OC style. This
config container inherited the r/o attributes of it's parent as a result.

We have a few options here:

1. Move config=false down to the state container and leave the entire list as
   r/w potentially accomodating future configuration (There could potentially
   be some attributes that you could tag an ID with in some implementations to
   suppress, change behavior, etc..)
2. Keep the entire hierarchy as config=false and thus remove any possibility
   for configuration. This is similar to other hierarchies such as /system/cpus

Platform Implementations

N/A: Bug

[dplore]

/gcbrun

[OpenConfigBot]

No major YANG version changes in commit cb68be2