Database error, "currently_active" is of type boolean but expression is of type integer

### Description

My homeserver logs and postgres logs shows errors regarding "currently_active" not being a correct type. I'm not sure if this has any grave effects on my system, but it worries me to see.

### Steps to reproduce

- Run version 1.140 or perhaps previous to 1.138
- Observe the logs

### Homeserver

lagy.org

### Synapse Version

1.140.0

### Installation Method

Other (please mention below)

### Database

apk add synapse

### Workers

Single process

### Platform

Alpine Linux 3.22.2

### Configuration

Nothing unusual to my knowledge

### Relevant log output

```shell
Too much log text to paste here. See log files below.
```

### Anything else that would be useful to know?

[homeserver.log](https://github.com/user-attachments/files/22966342/syn.log)
[postgres.log](https://github.com/user-attachments/files/22966343/syn-postgres-errors.log)

Start by reviewing the attached homeserver.log and postgres.log, then reproduce the error with Synapse 1.140. Trace the use of currently_active and determine why PostgreSQL receives an integer for a boolean value. Done means the error no longer appears and regression coverage verifies the corrected type.

Written by the indexing model from the issue text.