fix: make bindActionCreators thunk example runnable

[narutamaaurum]

Summary

• add redux-thunk to the playground store middleware chain so the delayed counter example can dispatch thunks at runtime
• add a regression test covering the FCCounterConnectedBindActionCreators increment flow

Validation

• cd playground && export CI=true && npm test -- --runInBand --watch=false src/connected/fc-counter-connected-bind-action-creators.spec.tsx
• cd playground && npm run tsc
• cd playground && npx eslint src/store/store.ts src/connected/fc-counter-connected-bind-action-creators.spec.tsx

Closes #212

[gemini-code-assist]

Code Review

This pull request introduces a new test suite for the connected counter component and integrates redux-thunk middleware into the global store. The review feedback suggests several improvements to the test file, including replacing the any type in the mock reducer with a more specific action type, removing redundant cleanup() calls that are automatically handled by the testing library, and adopting more idiomatic screen.getByText assertions for better clarity and robustness.

[gemini-code-assist]

Using any for the action parameter in the reducer disables type checking. It is recommended to use a more specific type, such as RootAction from MyTypes or at least { type: string }, to maintain type safety even in test mocks.

Suggested change

	reduxCounter: (state: number = 0, action: any) => {
	reduxCounter: (state: number = 0, action: { type: string }) => {

[gemini-code-assist]

The cleanup() call is redundant because @testing-library/react automatically performs cleanup after each test when used with Jest. This block can be simplified.

afterEach(() => {
  jest.useRealTimers();
});

[gemini-code-assist]

Using screen.getByText with a template literal is more direct and idiomatic than using a regex and checking textContent separately. Since getByText throws if the text is not found, the assertion is also more robust.

Suggested change

	expect(screen.getByText(RegExp(label)).textContent).toBe(label + ': 0');
	expect(screen.getByText(`${label}: 0`)).toBeDefined();

[gemini-code-assist]

Similar to the previous assertion, using a direct string match with screen.getByText is preferred for clarity and precision.

Suggested change

	expect(screen.getByText(RegExp(label)).textContent).toBe(label + ': 1');
	expect(screen.getByText(`${label}: 1`)).toBeDefined();

[narutamaaurum]

Addressed the review suggestions in 9d36ac4. The regression spec now uses AnyAction instead of any, drops the redundant explicit cleanup(), and switches to direct screen.getByText assertions while keeping the thunk timing check intact. Validation: CI=true npm test -- --runTestsByPath src/connected/fc-counter-connected-bind-action-creators.spec.tsx --watch=false and npm run tsc -- --noEmit.