Description Of Changes

Fix issue where very long title cause an horizontal scroll in the privacy request detail page.

Code Changes

• Removed headerLeft wrapper as it was not needed
• Adjusted styling for Privacy Request page
• Adjusted styling for activity entry, ensuring no wrap and that all children don't shrink
• Adjusted styling for activity entry title, removing arbitrary 33% max width in favor of displaying full width and shrink with ellipsis when needed
• Adjusted styling for activity entry timestamp, allowing ellipsis in smaller screens

Steps to Confirm

1. Visit https://fides-plus-nightly-git-eng-1042-privacy-request-d-f68fb7-ethyca.vercel.app/privacy-requests/pri_a66acfbd-d67a-4aa9-b451-62a0b8da3f1d use nightly build credentials for login
2. Using responsive mode in the browser, check that across multiple desktop screen sizes:
   a. A horizontal scroll should never occur
   b. when the entry has a short title, every part of the entry (author, title, date, tag) displays one after the other, leaving empty space to the right, like this:

c. when the entry has a really long title, every part of the entry (author, title, date, tag) displays one after the other completely filling the entire width of the activity tab. the title shrinks and expands to display as much text as possible before showing the ellipsis (...) like this:

(Local testing quick alternative)
Testing locally, the issue can be reproduced by editing the ActivityTimelineEntry.tsx file and repeating the {title} a bunch of times or setting it to a really long string.

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required