Fix link to array-api documentation

[bgawrych]

Description

Link check fails in multiple PR's, e.g.:
#20772 - https://github.com/apache/incubator-mxnet/runs/4467893604?check_suite_focus=true
#20713 - https://github.com/apache/incubator-mxnet/runs/4458865888?check_suite_focus=true

[mxnet-bot]

Hey @bgawrych , Thanks for submitting the PR
All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:

• To trigger all jobs: @mxnet-bot run ci [all]
• To trigger specific jobs: @mxnet-bot run ci [job1, job2]

---

CI supported jobs: [unix-cpu, clang, unix-gpu, edge, centos-cpu, miscellaneous, windows-cpu, sanity, centos-gpu, windows-gpu, website]

---

Note:
Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin.
All CI tests must pass before the PR can be merged.

[barry-jin]

Thanks for the fix!

[bgawrych]

@mxnet-bot run ci [centos-gpu]

[mxnet-bot]

Jenkins CI successfully triggered : [centos-gpu]

[bgawrych]

@barry-jin Do you know if something has change in the infrastructure of CI that can causing these timeouts in mkl continuous build? I belive it's not caused by any recent commit

[barry-jin]

@barry-jin Do you know if something has change in the infrastructure of CI that can causing these timeouts in mkl continuous build? I belive it's not caused by any recent commit

Looks like it is caused by macos-latest virtual-environment in github actions switched to use macOS-11 (previously macOS-10.15)

[bgawrych]

I have noticed this also - I will prepare PR to use latest working version to unblock CI and create issue tracker for this
Thanks @barry-jin

[barry-jin]

I have noticed this also - I will prepare PR to use latest working version to unblock CI and create issue tracker for this Thanks @barry-jin

I have created the quick fix #20777