Add links to documentation to ApiResource properties

[edamov]

Q	A
Bug fix?	no
New feature?	no
BC breaks?	no
Deprecations?	no
Tickets	fixes api-platform/docs#868
License	MIT
Doc PR	api-platform/docs#...

I started work on api-platform/docs#868 because it was marked as good first issue :)
First, I added links to documentation for API Resource properties and sort properties alphabetically.

But there are some points I don't understand from this issue.
What should we do with @see https://github.com/Haehnchen/idea-php-annotation-plugin/issues/112 in the class ApiResource?
I found this PR but still can't understand.

[teohhanhui]

What should we do with @see Haehnchen/idea-php-annotation-plugin#112 in the class ApiResource?

Nothing. 😄 But it's less important than the link to documentation entry, so keep it below.

[teohhanhui]

Hmm... Actually, this does not address api-platform/docs#868, but I think this is something worth doing as well. WDYT @dunglas?

[teohhanhui]

Thanks for squashing! 😄

Can you target 2.5 instead?

git reset --hard origin/2.5
git cherry-pick 254074a

[edamov]

Thanks for squashing!

Can you target 2.5 instead?

git reset --hard origin/2.5
git cherry-pick 254074a

oops. I do something in a wrong way

[teohhanhui]

I can take care of it if you'd like. 😄

[edamov]

I need to try :)

[edamov]

It got only worse 🤕 Now it has conflicts

[teohhanhui]

Did you try following the steps I've provided? 😄

[edamov]

Yes. But I had no success :( I had for some reasons second master branch

[teohhanhui]

Okay, no worries. I'll take care of this.

[edamov]

Thanks a lot for your help and your time!

[teohhanhui]

Note for next time: Always use a topic branch (e.g. feature/api-resource-annotation-link-docs) when creating a PR. Do not use the master branch (or others like 2.5).

[teohhanhui]

Thanks @edamov! 🎉