<!--- Provide a general summary of your changes in the Title above -->

## Description

When a custom tick component is rendered, ensure that the
'recharts-cartesian-axis-tick-value' class name is included.
(along with any existing className specified by the user if needed)

## Related Issue

#5738 

## Motivation and Context

When using a custom X-axis tick component (a user-defined component
passed to the tick prop of XAxis), the CSS class
(recharts-cartesian-axis-tick-value) that Recharts internally uses to
measure text size is not properly applied (passed) to this custom tick
component, resulting in text being cut off due to text size calculation
errors, especially when the font-size of the body is different from the
default value.

## How Has This Been Tested?

After modifying the library, I tested it in a local environment using
npm link and vite config.

enviroment
1. windows 11(desktop), chrome
2. MacOS Sequoia(mac m1 pro 16inch), chrome
3. MacOS Sequoia(mac m1 pro 16inch), safari

## Screenshots (if appropriate):

Windows 11, Chrome
<img width="487" alt="Screenshot 2025-05-13 at 9 19 46 PM"
src="https://github.com/user-attachments/assets/9a2fd43e-6d20-4a6b-866e-af0644d503bb"
/>

MacOS Sequoia, Chrome
<img width="487" alt="Screenshot 2025-05-13 at 9 19 46 PM"
src="https://github.com/user-attachments/assets/97166a1e-e71f-4656-81c1-8223cf27fd80"
/>

MacOS Sequoia, Safari
<img width="512" alt="Screenshot 2025-05-13 at 9 20 43 PM"
src="https://github.com/user-attachments/assets/7e7aa815-8709-489c-b131-7257b770f888"
/>

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [x] 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 change)

## Checklist:

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added tests to cover my changes.
- [ ] I have added a storybook story or extended an existing story to
show my changes

…s (2.x) (#5946)

## Description

A Bar's `minPointSize` attribute can be a function. This PR is aimed at
allowing to pass `null` or `undefined` values to this function (rather
than throwing)

## Related Issue

#5944 

## Motivation and Context

Null or undefined are valid values for datapoints, and are distinct from
`0` (i.e. the absence of data). It's interesting to allow to use those
values even if using a `minPointSize` function.

## How Has This Been Tested?

I tested the fork with a local dataset with null values, and a
minPointSize function returning different values for null non-null
values:

```
const minPointSize = useCallback((value: number | null, _index: number) => isNil(value) ? 0 : 2, []);
```

Other than that, there is little risk of side-effects:
- for existing `minPointSize` functions taking number values, the
function will continue working as is.
- if someone has a codebase sending null values to `minPointSize`,
rechart currently throws.
- minPointSizeCallback is only called at one place in the rechart code,
so there's no other impact
 
## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)

## Checklist:

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have added tests to cover my changes.
- [ ] I have added a storybook story or extended an existing story to
show my changes

…-10044504) (#5969)

## Description
Updates @babel/runtime dependency to resolve a Regular Expression Denial
of Service (ReDoS) security vulnerability identified by Snyk.

## Related Issue
Addresses security vulnerability SNYK-JS-BABELRUNTIME-10044504 in
@babel/[email protected]

## Motivation and Context
The vulnerability exists in the dependency chain: recharts →
react-smooth → react-transition-group → @babel/[email protected]. This
version of @babel/runtime contains a ReDoS vulnerability that could
potentially be exploited. The fix upgrades to @babel/[email protected]
which resolves the security issue.

## How Has This Been Tested?
- ✅ `npm run test` - All existing tests pass
- ✅ `npm run build` - Build completes successfully  
- ✅ `npm run lint` - No linting issues
- ✅ `npm ls @babel/runtime` - Confirms all dependencies use secure
version 7.27.6
- ✅ Verified no breaking changes to public API

## Types of changes
- [x] 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 change)

## Checklist:
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have added tests to cover my changes. (Security fix - existing
tests verify no regressions)
- [ ] I have added a storybook story or extended an existing story to
show my changes (Not applicable for dependency update)