Desired stack id is not updated for Rolling Upgrade

After Rolling Upgrade is performed, Desired Stack id is not updated in clusters table. We should update it otherwise many subsequent operations present undesired behavior e.g. if desired stack id is not updated after successful upgrade from stack 2.2 to 2.3, any new service onboarding to stack 2.3 fails since Ambari tries to onboard new service to stack 2.2(old desired stack id, where new service code might not be present)