tree 74c3cea5a5da1e0e35994efa97d9a11f0d7bc0cb
parent e1017305e3b0f51048ab7362c52dc6b851789f38
author Boris Zbarsky <bzbarsky@apple.com> 1671633772 -0500
committer GitHub <noreply@github.com> 1671633772 -0500
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJjoxtsCRBK7hj4Ov3rIwAAVqwIAAm+fJj0uH6JKeU4l1CSgSzf
 gFqB7++6a+sEppKdx869AJWqvUtIrirKEoVXF0W0AV7hTG6m2p0Lf6WCMfASitwA
 vG7MC0jYgqS0PSldxw+Oct+Xij8q01gJeppNZIcmbeqUmzCzx0jbkOLLf/qbq4D3
 w83ySbhBFMPCQPOTcDOxJB/NccNjHTdrkDW9wwjhBUFNPdVoMl59pxj/1dEVmqdc
 w0U+Ef5zFlvag0gnd/yEl8Y0R5n/bLQutHRg8Qbly40/nX7UWzma2cKR5LcuWwDZ
 4Tp77Z39nw1+N4pU6uJKrxbFxB4TUFpI9MQMA3LyX1PJgoL+3rrerDQVS2fnIBI=
 =aaoJ
 -----END PGP SIGNATURE-----
 

Go back to using the storage key 1.0 used for group fabric info. (#24163)

https://github.com/project-chip/connectedhomeip/pull/23409 changed the key under
which we store group fabric info, which breaks reception of group messages if a
node updates from before that change to after that change.

We should just keep using the same key name, especially because sharing a single
storage key for all possible fabric lists (groups and whatever else will want to
store lists of fabric indices) does not necessarily make sense.

Fixes https://github.com/project-chip/connectedhomeip/issues/24161