Use commons dependency management of okhttp version

Description

This issue does not include a description.

Contributor guide

Tech stack

java

Domain

backendapi

Issue type

chore

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

unclear

Prerequisites

Maven/Gradle dependency managementSpring Cloud project conventions

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

25

Research direction

The issue proposes using a commons dependency management for the okhttp version. The body is empty, so review the two comments for details. If not available, examine the project's pom.xml or build.gradle files to see how dependencies are currently managed, and check if there is a parent POM or BOM that centralizes versions. Then propose changes to align okhttp versioning with that common management.