Add shared mutex to KC Client and enforce locking for Realm Client Profiles and Policies

[rhigdon]

Adds an additional profile and policy to the example realm
adds a shared mutex to use with the Keycloak Client
use this mutex when creating/updating realm client policies and profiles

[sschu]

@rhigdon Thanks for your contribution! Can you elaborate what problem you want to solve by adding the mutex to the client?

[rhigdon]

@rhigdon Thanks for your contribution! Can you elaborate what problem you want to solve by adding the mutex to the client?

Hey @sschu -- I was going to create an issue for this but have not yet. Currently, when creating more than one Client Profile or Client Policy for a realm there is a race condition. Both resources try to update all policies or profiles for a realm.. so there becomes a race condition and only one is updated. This will ensure that things are added serially.