API path configurations need to be more comprehensive optionally

[ashendes]

Description:
Currently, only the base API path of the Choreo APIs are requested as a configurable.
The API path configurations need be more comprehensive because,

1. Any customized APIs may have different context paths and users will have to manually update the API paths in the source code if this happens
2. Updates to the APIs could be reflected in separate versions. There is no way to update the API version in the URLs without changing the source code manually.

Users should be given the option to update the individual API paths if required.

[1]

asgardeo-enterprise-ciam-sample/src/apps/kfone-website/src/api/index.js

Line 116 in 2b7d6ce

url: `${BASE_URL}/usage-data-api/1.0.0/packageRecommendation`