Tick rotation/autoSkip calculations assume full space is used

## Expected Behavior
Tick/Label size and space calculations should take into account where the labels start/stop, and use that information to calculate a more approximate measure of label space.

## Current Behavior
Tick calculations assume they start and stop at the full size of the axis, which is not always the case.

This is most obvious in small usecases - both small sizes and small number of labels - as these are the cases where the disparity between "real" and calculated tick space, sizes and distances is greatest.
A good example is time scales using "week" as the unit, where the days may not match the points where the weeks start exactly, so a relatively large empty (tickless) space can exist st the edges of the chart.

## Possible Solution
The scale's `getPixelForValue` will likely need to be used in the `calculateLabelRotation`/`autoSkip` functions, but I didn't do enough research yet to determine all possible implications of this.

## Steps to Reproduce
Live example: https://codepen.io/tiagoroldao/pen/mdwEMoG


## Context
This was detected while using chartJS to create small widgets on a dashboard. These are often small charts with time data (i.e. "last 30 days") where this is a common

## Environment
* Chart.js version: 3.5.1