[Feature Request] Add additional fields to exported docs

還沒有人認領這個 Issue。

Right now, it's very difficult to parse the exported docs. I've mostly been able to figure stuff out, but there's a bit of information the exported JSON file does not expose, which I would like to suggest.

- A field for which class something originates from, to filter out unchanged methods/fields from parents
- A relative version of `file`, instead of an absolute path
- [x] A version of the description which does not include markdown for params and return values, since those are separate
- Whether a function is deprecated or not
- A way to hide a field or method from the docs export (`---@nodoc`?)
- Maybe a way to not export inherited fields/methods? The exported file for my project is more than a million lines long...

先找到匯出的文件 JSON 實作，以及為函式、方法和欄位組合欄位的程式碼。檢視目前如何表示繼承、檔案路徑、描述和棄用；完成的條件是確定一致同意的範圍，並加入涵蓋所選匯出欄位以及 nodoc 或繼承行為的測試。

由索引模型根據 Issue 內容生成。