feat(message-expiry): Add message expiry msg on the right side bar

[existentialcoder]

☑️ Resolves

• Fix Chat should permanently indicate whether message expiration is set up #7953
• Add message expiration message on the right side bar for individual and group chats

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

🏚️ Before	🏡 After
Personal
Group

|

🏁 Checklist

• 🌏 Tested with different browsers / clients:
  • Chromium (Chrome / Edge / Opera / Brave)
  • Firefox
  • Safari
  • Talk Desktop
  • Integrations with Files sidebar and other apps
  • Not risky to browser differences / client
• 🖌️ Design was reviewed, approved or inspired by the design team
• ⛑️ Tests are included or not possible
• 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required

[nickvergessen]

instead of calculating a random date that would need live updating, I would show something like: "Message expiration is set to 30 minutes"

[existentialcoder]

That is rather the actual expiration timestamp coming from conversation.lastMessage.expirationTimestamp. Should we still replace it in terms of number of minutes / hours / days?

[Antreesy]

Yes, it should indicate duration

[Antreesy]

This part should be enough, the whole logic doesn't belong to RightSidebar.vue, and does not need props to be passed. We already have a conversation object here, maybe just need to be rearranged:

const profileInformation = computed(() => {
	const fields = []

	if (profileInfo.value?.role || profileInfo.value?.pronouns) {
		...
	if (profileInfo.value?.organisation || profileInfo.value?.address) {
		...
	if (conversation.value.messageExpiration) {
		fields.push({
			key: 'message-expiry',
			icon: IconDeleteClockOutline,
			label: t('spreed', 'Message expiration set: {duration}', { duration: expiration.label }),
		})
	}

	return fields
}

duration string can be composed from strings here

spreed/src/components/ConversationSettings/ExpirationSettings.vue

Lines 61 to 66 in e35af19

	{ id: 3600, label: n('spreed', '%n hour', '%n hours', 1) },
	{ id: 28800, label: n('spreed', '%n hour', '%n hours', 8) },
	{ id: 86400, label: n('spreed', '%n day', '%n days', 1) },
	{ id: 604800, label: n('spreed', '%n week', '%n weeks', 1) },
	{ id: 2419200, label: n('spreed', '%n week', '%n weeks', 4) },
	{ id: 0, label: t('spreed', 'Off') },

'Message expiration set: {duration}' is already existing and translated string, so we e.g. can backport it to older versions right away

[Antreesy]

This is the place, thanks for finding

[Antreesy]

IMO although it's good to have a test coverage, it doesn't worth it in this case. Efforts to write / review tests for this exceed the implementation of the feature, that should be just a piece on top of already working code