Update awesome_print to 1.8.0
What does this MR do?
Updates awesome_print from 1.2.0 to 1.8.0.
Are there points in the code the reviewer needs to double check?
No.
Why was this MR needed?
To keep dev packages up to date.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Tests passed for this feature/bug - Conform by the code review guidelines
-
Has been reviewed by a Backend maintainer
-
-
Conform by the merge request performance guides -
Conform by the style guides
What are the relevant issue numbers?
Closes #46844 (closed)
Edited by Takuya Noguchi