chore(ci): Update automated-release.yml

[markscott-ms]

The semantic release notes step is failing. Updating to a method that will import the module correctly.

Description

Currently the automated release is failing with:

Failed to generate release notes via semantic-release dry run
TypeError: semanticRelease is not a function
    at [eval]:1:108
    at [eval]:1:462
    at runScriptInThisContext (node:internal/vm:209:10)
    at node:internal/process/execution:446:12
    at [eval]-wrapper:6:24
    at runScriptInContext (node:internal/process/execution:444:60)
    at evalFunction (node:internal/process/execution:279:30)
    at evalTypeScript (node:internal/process/execution:291:3)
    at node:internal/main/eval_string:74:3

Updating to a method that works for importing semanticRelease:

$ node                                                                                                           
Welcome to Node.js v22.16.0.
Type ".help" for more information.
> const { default: semanticRelease } = await import('semantic-release')
undefined
> await semanticRelease({dryRun: true, ci:false})
[10:52:55 AM] [semantic-release] › ℹ  Running semantic-release version 24.2.7

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📚 Documentation update
• 🎨 Code style/formatting changes
• ♻️ Refactoring (no functional changes)
• ⚡ Performance improvements
• ✅ Test additions or updates
• 🔧 Chore (maintenance, dependencies, CI, etc.)

Affected Components

• CLI (cli/)
• Shared (shared/)
• CALM Widgets (calm-widgets/)
• CALM Hub (calm-hub/)
• CALM Hub UI (calm-hub-ui/)
• Documentation (docs/)
• VS Code Extension (calm-plugins/vscode/)
• Dependencies
• CI/CD

Commit Message Format ✅

Testing

• I have tested my changes locally
• I have added/updated unit tests
• All existing tests pass

Checklist

• My commits follow the conventional commit format
• I have updated documentation if necessary
• I have added tests for my changes (if applicable)
• My changes follow the project's coding standards