Used resource title instead of resource type in page title.

[Faakhir30]

• I signed and returned the Plone Contributor Agreement, and received and accepted an invitation to join a team in the Plone GitHub organization.
• I verified there aren't other open pull requests for the same change.
• I followed the guidelines in Contributing to Volto.
• I succesfully ran code linting checks on my changes locally.
• I succesfully ran unit tests on my changes locally.
• I succesfully ran acceptance tests on my changes locally.
• If needed, I added new tests for my changes.
• If needed, I added documentation for my changes, either in the Storybook or narrative documentation.
• I included a change log entry in my commits.

---

If your pull request closes an open issue, include the exact text below, immediately followed by the issue number. When your pull request gets merged, then that issue will close automatically.

Closes #6308

[netlify]

✅ Deploy Preview for plone-components canceled.

Name	Link
🔨 Latest commit	bca33bc
🔍 Latest deploy log	https://app.netlify.com/sites/plone-components/deploys/670fe530ed65cf0007eb78ce

[stevepiercy]

This needs review from @plone/volto-team. I'm not sure about inserting a - into the message ID. I don't know if that would be good, bad, or doesn't matter for a11y, @plone/volto-accessibility?

[JeffersonBledsoe]

I'm not sure about inserting a - into the message ID. I don't know if that would be good, bad, or doesn't matter for a11y, @plone/volto-accessibility?

No problems that I'm aware of. It's a common pattern to use it to separate out 'sections' of a title and most screen readers will skip over it and add a gap in the read-out.

All that said, I'm not sure it's a needed change here (as already mentioned) as we don't use it elsewhere so let's keep it consistent