Initial support for #686. #705

Related: https://github.com/louislam/uptime-kuma/issues/686

Initial implementation. Please advice.

Done:

All query params sent in /api/push/ except for msg and ping are considered tags to update;
Non-existing tags are ignored;
Do not put additional database pressure if no tags are passed.

To fix:

When using trx.dispense() the returning Bean fails on bean.toJSON() call. Using R.dispense() for now;
What callback should be sent to the UI for updating tag values? Currently the code is updating the database but the new tag values are only updated after a page refresh 😢 .

Rebased with latest master.

Previously I relied on monitorList to update tags because of infrequent use. I guess we can add a new event in /src/mixins/socket.js specifically for updating tags?

Please add Related: https://github.com/louislam/uptime-kuma/issues/686 to your first message

Issue in title is not clickable
And adding URL in first message will also connect your PR with issue in right sidebar

Rebased with latest master. Support for duplicated tags (updates the oldest one).

Why beans returned from R.findOne(), R.dispense(), etc. are different from the ones returned from transactions? (trx.findOne(), trx.dispense(), ...)

With the latest rebase with master, this PR has now two occurrences of this problem. I have to use R. instead of trx. to access .toJSON()

I'm new to this codebase. Please advice.

I would suggest that it should be implemented without transaction at this moment.

I found that transaction is stable only if it is a raw query.

Rebased with latest master. Removed transaction support.

What callback should be sent to the UI for updating tag values?