Typescript: Strict compile option for codemods package

[aditya1]

Migrates @storybook/codemod from #22176

Problem Statement
Packages in StoryBook mono-repo use Typescript. Although, some of them use typescript in non-strict fashion. This PR focuses on codemod package and turns on the strict mode.

What I did

I migrated @storybook/codemod to use strict:true in typescript compiler options. It will enable better type-checking for this package. I've fixed most of the errors which were occurring after changing the strict flag to true. But in some cases, I've used the ts-ignore flag since the code flow was difficult to understand. And as per the issue description, for these PRs changes should not be non-functional, hence I decided to use ts-ignore. Mostly, added ts-ignore at places where function arguments aren't matching.

How to test

For testing, I ran all the existing Unit Tests and E2E Tests. This is a non-functional, non-breaking change running unit tests and E2E tests are sufficient for the testing.

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

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

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