Currently in standalone mode, it is possible to load multiple components
with the same name but of different types. This is problematic as it can
produce undefined behaviour in Daprd where global state indexed on
Component name (like state encryption) can "leak" to another Component.
It also makes it impossible to implement the hot reloader reconciler as
that controller is level based, and without a single unique name to
index on, the reconciler cannot determine which Components have been
deleted/editted. It is also confusing to different requirements to
Kubernetes whether a Component name _must_ be unique within a namespace.

PR implements a check to ensure that Component names are unique. The
component store implements a pending & lock mechanism to ensure that
another Component of the same name cannot be added whilst another is
initialising.

Adds an integration test to ensure daprd errors when multiple Components
with the same name are added.

Signed-off-by: joshvanl <me@joshvanl.dev>

Signed-off-by: joshvanl <me@joshvanl.dev>

Signed-off-by: joshvanl <me@joshvanl.dev>