fix: resolve duplicate story IDs in visual-stories executor

- Use theme.value instead of theme.title in story titles for consistency
- Add theme identifier to export names to ensure uniqueness across themes
- Export names now include theme: BusyIndicatorSapHorizonVisuals vs BusyIndicatorSapFiori3Visuals
- Resolves 'Duplicate stories with id' errors in Chromatic builds
- Storybook build now completes successfully without conflicts [ci visual]

Author: droshev

packages/workspace-plugins/src/executors/visual-stories/index.ts

@@ -57,14 +57,14 @@ export default async function(schema: VisualStoriesSchema, context: ExecutorCont
         import { visualStory, withThemeProvider } from 'fundamental-styles/storybook';
         
         export default {
-            title: ${JSON.stringify('Visuals/' + fullTitle + '/' + theme.title)},
+            title: ${JSON.stringify('Visuals/' + fullTitle + '/' + theme.value)},
             parameters: {
                 theme: ${JSON.stringify(theme.value)},
                 packageId: ${JSON.stringify(projectName)},
             },
             decorators: [withThemeProvider]
         };
-        export const ${className}Visuals = visualStory(stories as any);
+        export const ${className}${names(theme.value).className}Visuals = visualStory(stories as any);
         `,
                 { parser: 'typescript' }
             );