bus/peer: properly initialize peer-charges
bus/peer: properly initialize peer-charges

It is unclear to me what `{ .foo[0] = bar, .foo[1] = baz }` does as
designated initializer. Use the canonical form `{ .foo = { bar, baz } }`
to avoid ambiguities.

We had reports about uninitialized charges on `peer->charges[0]`, so
lets see whether this fixes things. Tests did not indicate any
difference and the previous initializer should be correct. But lets be
sure and consistent.

Signed-off-by: David Rheinsberg <1e7ff67ac6e6692b085f67edeb10803d9022c525@gmail.com>

bus1/dbus-broker