SRVKP-11123: Upgrade dependencies and resolve TypeScript, i18n and CI job issues

[anwesha-palit-redhat]

Dependency upgrades

• Upgrade @openshift/dynamic-plugin-sdk ^4.0.0 → ^8.1.0, dynamic-plugin-sdk-extensions ^1.3.0 → ^1.4.0, dynamic-plugin-sdk-utils ^4.1.0 → ^5.0.1
• Add @patternfly/react-styles and react-router as explicit dependencies (previously missing from package.json)
• Upgrade eslint-plugin-react-hooks 4.1.2 → ^4.6.0 — adds eslint 8.x to its supported peer dependency range
• Upgrade stylelint-config-standard ^31.0.0 → ^36.0.0 — bumps its peer dep requirement to stylelint ^16.x
• Upgrade i18next-parser ^3.11.0 → ^9.3.0
• Upgrade formik 2.0.3 → ^2.1.5
• Lower NODE_OPTIONS max old space from 6144 to 4096 MB

TypeScript fixes

• Change nameValidationSchema parameter type from TFunction to (key: string, options?: TOptions) => string — the function only calls t(string), so requiring the full branded TFunction type was unnecessarily strict and caused a type error when passing the plain t wrapper from common-utils
• Fix Trans interpolation in RemoveTriggerForm and TriggerTemplateSelector — use i18nKey + values + components props instead of object literal {{ varName }} children inside <b> tags, which are rejected by newer react-i18next TypeScript types

i18n pluralization fix

• Rename count → value in t() calls in details-page.tsx, utils.ts, dateTime.ts, and events.jsx where the number is used purely for interpolation, not for singular/plural variation. count is a reserved i18next keyword that triggers automatic plural key generation, causing CI failures when i18next-parser v9 changed the plural format from _plural to CLDR _one/_other
• Update locale file to reflect the renamed interpolation keys

[openshift-ci-robot]

@anwesha-palit-redhat: This pull request references SRVKP-11123 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@anwesha-palit-redhat: This pull request references SRVKP-11123 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@anwesha-palit-redhat: This pull request references SRVKP-11123 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Dependency upgrades

• Upgrade @openshift/dynamic-plugin-sdk ^4.0.0 → ^8.1.0, dynamic-plugin-sdk-extensions ^1.3.0 → ^1.4.0, dynamic-plugin-sdk-utils ^4.1.0 → ^5.0.1
• Add @patternfly/react-styles and react-router as explicit dependencies (previously missing from package.json)
• Upgrade eslint-plugin-react-hooks 4.1.2 → ^4.6.0 — adds eslint 8.x to its supported peer dependency range
• Upgrade stylelint-config-standard ^31.0.0 → ^36.0.0 — bumps its peer dep requirement to stylelint ^16.x
• Upgrade i18next-parser ^3.11.0 → ^9.3.0
• Upgrade formik 2.0.3 → ^2.1.5
• Lower NODE_OPTIONS max old space from 6144 to 4096 MB

TypeScript fixes

• Change nameValidationSchema parameter type from TFunction to (key: string, options?: TOptions) => string — the function only calls t(string), so requiring the full branded TFunction type was unnecessarily strict and caused a type error when passing the plain t wrapper from common-utils
• Fix Trans interpolation in RemoveTriggerForm and TriggerTemplateSelector — use i18nKey + values + components props instead of object literal {{ varName }} children inside <b> tags, which are rejected by newer react-i18next TypeScript types

i18n pluralization fix

• Rename count → value in t() calls in details-page.tsx, utils.ts, dateTime.ts, and events.jsx where the number is used purely for interpolation, not for singular/plural variation. count is a reserved i18next keyword that triggers automatic plural key generation, causing CI failures when i18next-parser v9 changed the plural format from _plural to CLDR _one/_other
• Update locale file to reflect the renamed interpolation keys

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[arvindk-softwaredev]

nit: will this affect HMR in local?

[anwesha-palit-redhat]

Yes it will. It will fail with the same error we faced earlier, therefore I left the code and commented it, so that during dev we can uncomment this and run. If they fix the issue in the later versions of @openshift-console/dynamic-plugin-sdk-webpack then we can remove this altogether. What do you think ?

[arvindk-softwaredev]

agreed, we can use this in local development and check for this in later versions of @openshift-console/dynamic-plugin-sdk-webpack

[arvindk-softwaredev]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anwesha-palit-redhat, arvindk-softwaredev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [anwesha-palit-redhat]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment