Better description for Shrink Database button

[Saibamen]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

As discussed in #2470 (comment)

Previous description suggested that you need to recreate your database from scratch.

Type of change

Please delete any options that are not relevant.

• Other

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
• My changes generates no new warnings
• My code needed automated testing. I have added them (this is optional task)

[CommanderStorm]

Changing the meaning of a translation is not great, as this leaves the translators unaware of this change.

A better approach would be to introduce a translation string and remove the current one.
This also allows using the i18n-t-component to display VACUUM/AUTO_VACUUM as <code>VACUUM</code>/<code>AUTO_VACUUM</code>
Here is the relevant line:

uptime-kuma/src/components/settings/MonitorHistory.vue

Line 35 in cf2d603

<div class="form-text mt-2 mb-4 ms-2">{{ $t("shrinkDatabaseDescription") }}</div>

[Saibamen]

Changing the meaning of a translation is not great, as this leaves the translators unaware of this change.

I translated via Weblate and I bet that I translated few already translated i18n keys with changed English source.

But I like to have HTML's <code>. I will change that today. Thanks

[CommanderStorm]

I have made a few changes.
Given that you touched the other translation files, this PR can only be merged directly after merging #4436 and #4394 to avoid merge conflicts being created in Weblate.

[CommanderStorm]

There may be other merge conflicts that come up. v2.0 does support mariadb next to sqlite, but said db still needs to be integrated here as well

[Saibamen]

This PR is for 1.23.x only

[louislam]

Since merging conflicts on Weblate is painful, as the git repo is read only. And removing the key is likely causing this problem.

I think we need to find another way to "deprecated" this key instead of removing it.

[CommanderStorm]

I think this should not cause a merge-conflict if merged directly after #4436
Am I missing some context?

What might indeed be problematic is that users can't supply translations for v1.23.X, only for v2.X
=> this change will never get translated.

[louislam]

I think this should not cause a merge-conflict if merged directly after #4436 Am I missing some context?

Since it is for the 1.23.X branch, it will happen when I merge the 1.23.x branch to master, I believe.

Of course I can merge the 1.23.X branch to master after #4436, but it is kind of "soft-locked".

What might indeed be problematic is that users can't supply translations for v1.23.X, only for v2.X => this change will never get translated.

You are right. And 1.23.X is indeed not translatable in the current stage, as Weblate don't support for multiple branches. (Or I don't know how to set up)

For simplicity, I would suggest this pr should be merged into the master branch directly and also be merged after #4436.

[Saibamen]

Weblate don't support for multiple branches

@louislam:
https://docs.weblate.org/en/latest/faq.html#how-do-i-translate-several-branches-at-once