request_with_links() does not distinguish between multiple 'link' response headers

Some of the paginated API's, for example /users, return double 'link' headers in the response. It seems the request_with_links() doesn't distinguish between the two and depending on the order picks one of the two; which might lead to unexpected behaviour if the link is to 'self'.

See Okta::request_with_links:

async fn request_with_links<Out>(
        &self,
        method: http::Method,
        uri: &str,
        message: Message,
    ) -> ClientResult<(Option<crate::utils::NextLink>, crate::Response<Out>)>
    where
        Out: serde::de::DeserializeOwned + 'static + Send,
    {
        let response = self.request_raw(method, uri, message).await?;

        let status = response.status();
        let headers = response.headers().clone();
        let link = response
            .headers()
           // HERE: if there are two 'link' headers, which one is it getting?
            .get(http::header::LINK)
            .and_then(|l| l.to_str().ok())
            .and_then(|l| parse_link_header::parse(l).ok())
            .as_ref()
            .and_then(crate::utils::next_link);
...

Start at Okta::request_with_links and inspect how response.headers() handles repeated LINK values before parse_link_header::parse and crate::utils::next_link. Reproduce a response with two Link headers, then verify that pagination chooses the intended link consistently rather than depending on header order.