require-osd-release not set after upgrading to Quincy

[Ponnuvel Palaniyappan]

After upgrading to Quincy, the cluster produces:

```
$ ceph versions
{
    "mon": {
        "ceph version 17.2.0 (43e2e60a7559d3f46c9d53f1ca875fd499a1e35e) quincy (stable)": 1
    },
    "mgr": {
        "ceph version 17.2.0 (43e2e60a7559d3f46c9d53f1ca875fd499a1e35e) quincy (stable)": 1
    },
    "osd": {
        "ceph version 17.2.0 (43e2e60a7559d3f46c9d53f1ca875fd499a1e35e) quincy (stable)": 3
    },
    "mds": {},
    "overall": {
        "ceph version 17.2.0 (43e2e60a7559d3f46c9d53f1ca875fd499a1e35e) quincy (stable)": 5
    }
}

$ ceph -s
  cluster:
    id: 19ec8458-1e33-11ed-86f5-3933ed5eb400
    health: HEALTH_WARN
            mon is allowing insecure global_id reclaim
            all OSDs are running quincy or later but require_osd_release < quincy

  services:
    mon: 1 daemons, quorum juju-5c5bb9-focal-ceph-0 (age 46m)
    mgr: juju-5c5bb9-focal-ceph-0(active, since 46m)
    osd: 3 osds: 3 up (since 71m), 3 in (since 101m)

  data:
    pools: 2 pools, 129 pgs
    objects: 2 objects, 449 KiB
    usage: 76 MiB used, 30 GiB / 30 GiB avail
    pgs: 129 active+clean
```

'require-osd-release' doesn't get set to quincy as documented in the upgrade procedure [0].
It remains 'octopus':
```
$ ceph report | jq '.osdmap.require_osd_release'
report 193923920
"octopus"
```

Steps to reproduce:

1. Deploy an Octopus (used latest, which is as of now 15.2.16)

2. Upgrade to Pacific (16.2.9)

3. Then upgrade to Quincy (17.2.0)

[0] https://ceph.io/en/news/blog/2022/v17-2-0-quincy-released/