misc: remove border-bottom if test is isolated in studio mode

[kurekszymon]

• Closes UI: Border at bottom of test is not needed when in Studio mode #32478

Additional details

border bottom is not needed when run isolated in studio mode.

Steps to test

run a test in studio mode

How has the user experience changed?

before

after

PR Tasks

• [na] Have tests been added/updated?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[kurekszymon]

didn't know how to address misc section in in cypress-documentation as there are two ways of handling it, either with pr to main or to specific release.

if that's alright please advise on how to proceed, or chore/fix is enough for task like this.

i thought maybe I can group two tasks (if both are applicable) - the other one - with one change to either main or specific release in documentation.

[jennifer-shehane]

@kurekszymon For this one - this will be released to users using experimentalStudio, so 'misc' is appropriate for this PR. You would put the update in the cli/changelog.md in this PR.

[kurekszymon]

jennifer-shehane sorry for the mess with commits and force pushes - tried to ensure clean history, but checks keep on failing on semantic pr due to wrong release date. i suppose it just expects the format of xx/xx/xxxx; but i don't know where to look for it, and i most certainly don't know the release date.

edit: this is now obselete as proper release date came to cli/changelog.md resolved conflicts and commited proper misc section.

[mschile]

Looks good! Thanks for the contribution!