[DOC] Fix TOC indentations

[itaismith]

Description of changes

Tailwind doesn't support dynamic styling, so switching to a list of pre-defined indents for the table of contents component.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

Fix Table of Contents Indentation in Documentation Components

This PR addresses a UI issue in the table of contents component used in documentation. The change replaces dynamic styling (which doesn't work with Tailwind) with pre-defined indent classes for different heading levels, ensuring proper visual hierarchy in the documentation navigation.

Key Changes:
• Replaced dynamic indentation styling with predefined Tailwind classes
• Created an array of indentation classes for different heading levels
• Added overflow handling for the navigation container
• Improved the component's height management and spacing

Affected Areas:
• Documentation UI components
• Table of contents styling and rendering

This summary was automatically generated by @propel-code-bot