CSF-tools: Parse stories using typescript keywords 'satisfies' and 'as'

[joaonunomota]

Closes #22422

What I did

• Added if statements to retrieve correct node for story (similar to code for Meta node on line 271 of CsfFile.ts)
• Added test for parsing stories using typescript as keyword
• Updated test for parsing stories using typescript satisfies keyword, it was a mislabelled duplicate of the "" test

How to test

1. Run a sandbox for a typescript template, e.g. yarn task --task sandbox --start-from auto --template react-vite/default-ts
2. Update @storybook/csf-tools using yarn build
3. Update Button.stories.ts with the following:

export const Primary = {
  name: 'Primary (satisfies)',
  args: {
    primary: true,
    label: 'Button',
  },
} satisfies Story;

export const Secondary = {
  name: 'Secondary (as)',
  args: {
    label: 'Button',
  },
} as Story;

4. Open Storybook in your browser and confirm that they render correctly

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "build", "documentation", "maintenance", "dependencies", "other"]

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[kasperpeulen]

Thanks, looks good to me!