Move user_story.shared_user_story_state to story.shared_state

tools/telemetry/telemetry/user_story/user_story_set.py

Index: tools/telemetry/telemetry/user_story/user_story_set.py
diff --git a/tools/telemetry/telemetry/user_story/user_story_set.py b/tools/telemetry/telemetry/user_story/user_story_set.py
index e68b4ea685c7399517e6c308ee25329a83193db6..a0473d7d2447f946e259b737e8b83c9431765994 100644
--- a/tools/telemetry/telemetry/user_story/user_story_set.py
+++ b/tools/telemetry/telemetry/user_story/user_story_set.py
@@ -55,12 +55,12 @@ class UserStorySet(object):
   def allow_mixed_story_states(self):
     """True iff UserStories are allowed to have different StoryState classes.
 
-    There are no checks in place for determining if SharedUserStoryStates are
+    There are no checks in place for determining if SharedStates are
     being assigned correctly to all UserStorys in a given UserStorySet. The
     majority of test cases should not need the ability to have multiple
     ShareduserStoryStates, and usually implies you should be writing multiple
     benchmarks instead. We provide errors to avoid accidentally assigning
-    or defaulting to the wrong SharedUserStoryState.
+    or defaulting to the wrong SharedState.
     Override at your own risk. Here be dragons.
     """
     return False