fix: #3621380 Take the access-denied step from varbase-e2e 2.0.4

Issue: #3621380 Remove the local "am denied access to" step, now ambiguous with @vardot/varbase-e2e 2.0.4

Why

@vardot/varbase-e2e 2.0.4 ships the same step this project defined locally, so Cucumber saw two definitions for one sentence and failed the run with Multiple step definitions match — 4 of the 32 scenarios.

Then I am denied access to "/admin/config/ai/figma"

• Ours: tests/step-definitions/ai-figma.steps.js:89
• The library's: navigation.steps.js:264

What changed

• Deleted the local step and its doc block from tests/step-definitions/ai-figma.steps.js.
• Dependency ^2 → ^2.0.4, with package-lock.json refreshed.
• No feature file changes: the sentences are identical.

Keep the library one: it passes on any refusal a site can give (403, 404, an access-denied page, a redirect to the log-in form) and it is documented. Ours only checked the status code.

Verified

npx cucumber-js --dry-run: 32 scenarios, 149 steps, nothing ambiguous, nothing undefined (before: 4 ambiguous). The browser suite needs a live site, so CI confirms the rest.

AI-Generated: Yes

Checkpoints:

• File an issue
• Addition/Change/Update/Fix
• Testing to ensure no regression
• Automated unit testing coverage
• Automated functional testing coverage
• UX/UI designer responsibilities
• Readability
• Accessibility
• Performance
• Security
• Developer Documentation
• User Guide Documentation
• Reviewed by human
• Code review by maintainers
• Full testing and approval
• Credit contributors
• Review with the product owner
• Release notes snippet
• Release