Issue Summary

Using REST API v1, we are able to fetch certain "links" that correspond to a piece of content. Examples being: `editui`, `webui`, `tinyui`, etc.

An example being:

"_links":{
      "editui":"/pages/resumedraft.action?draftId=734397355",
      "webui":"/spaces/zmarkdown/pages/734397355/markdownPageUrlRelReplacementVars",
      "context":"/wiki",
      "self":"https://bobswift-prod.atlassian.net/wiki/rest/api/content/734397355",
      "tinyui":"/x/qwPGKw",
      "collection":"/rest/api/content",
      "base":"https://xxxxxxx.atlassian.net/wiki"
   } 

These links are not available from any of the V2 endpoints, but are necessary for parity

Steps to Reproduce

1. Fetch a page using V1 endpoint: /rest/api/content/{pageid}
2. Observe `_links` field
3. Try to this information using  /api/v2/pages/{pageid}
4. Notice these results are absent

Expected Results

The links fields are accessible from the V2 endpoints.

Actual Results

The links fields are absent from the V2 endpoints.

Workaround

No workaround besides using deprecated V1 endpoints.