remove Gradient links in README

[kerstink-GC]

Changelogs

• enumerate the changes of that PR.

---

Checklist:

• Was this PR discussed in an issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
• Add tests to cover the fixed bug(s) or the new introduced feature(s) (if appropriate).
• Update the API documentation is a new function is added, or an existing one is deleted.
• Write concise and explanatory changelogs above.
• If possible, assign one of the following labels to the PR: feature, fix or test (or ask a maintainer to do it for you).

---

discussion related to that PR

[codecov]

Codecov Report

Merging #505 (a190aba) into main (a8e715c) will increase coverage by 0.10%.
Report is 68 commits behind head on main.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #505      +/-   ##
==========================================
+ Coverage   71.42%   71.52%   +0.10%     
==========================================
  Files          93       93              
  Lines        8527     8708     +181     
==========================================
+ Hits         6090     6228     +138     
- Misses       2437     2480      +43     

Flag	Coverage Δ
unittests	71.52% <ø> (+0.10%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
ipu	49.14% <ø> (ø)