DOI Suffix Encoding for slashes (v1/) in Anthology DOI

### Confirm that this is a bug report

- [x] I want to report an issue that does _not_ concern paper or author metadata.
- [x] I have searched for similar existing issues first.

### Problem Description

Firefox 149.0 (aarch64) aka Mac OS 15.7.5 (PS added as requested, not where the bug happens)

Don't have a reproduction/scenario right now, will keep an eye out

e.g. https://aclanthology.org/2022.acl-long.568/

DOI works as both a link and and identifier
I have had trouble with non-central resolvers (doi.org) for DOIs that use the /v[number]/ format in ACL

Quick look at the DOI standards https://www.doi.org/doi-handbook/html/index.html indicates that (Section 3 of the handbook)
`/` is meant to have special function and the DOI should only split into two parts Prefix and Suffix with the `/` as the delimeter

Similarly that prefix and suffix need to also use percentage encoding (to avoid problems with special url chars such as `/`) (Section 3.7)

I tried the url encoded version of the URL - `10.18653/v1%2F2022.acl-long.568` gets resolved through web (as expected) but not as ID (as expected)

Currently, the non-urlencoded prefix ID (as seen in screenshot) also gets resolved so this is not a critical issue.

I am not very familiar with the DOI infrastructure Architecture (resolver etc.), but I expect using `/v1/` has some problems.

DOI Resolution docs also point this out - https://www.doi.org/the-identifier/resources/factsheets/doi-resolution-documentation#1-resolving-dois-using-the-proxy-server-system

> Note also that web browser treatment of “/./” and “/../” can be inconsistent. It is recommended that one of the slashes be percent encoded, e.g., change “/./” to “/.%2F” and “/../” to “/..%2F”.