mysql_query: correctly reflect changed status in replace statements

[unnecessary-username]

SUMMARY

There is a replace statement in MySQL and mariadb. Currently running replace statements works well except that the changed status is always false.
So I add REPLACE as a DML_QUERY_KEYWORDS and I supplement test cases for this.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

mysql_query

ADDITIONAL INFORMATION

[codecov]

Codecov Report

Merging #193 (6d55c36) into main (0fabb2b) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #193   +/-   ##
=======================================
  Coverage   76.92%   76.92%           
=======================================
  Files          20       20           
  Lines        1794     1794           
  Branches      439      439           
=======================================
  Hits         1380     1380           
  Misses        268      268           
  Partials      146      146           

Impacted Files	Coverage Δ
plugins/modules/mysql_query.py	89.02% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0fabb2b...6d55c36. Read the comment docs.

[Andersson007]

@unnecessary-username hi, thanks for the contribution!
Could you please fix sanity issues:

ERROR: tests/integration/targets/test_mysql_query/tasks/mysql_query_initial.yml:312:18: error: syntax error: mapping values are not allowed here (syntax)
ERROR: tests/integration/targets/test_mysql_query/tasks/mysql_query_initial.yml:312:18: unparsable-with-libyaml: None - mapping values are not allowed in this context

you can click on Details in the test box to see the details:)

[Andersson007]

LGTM

[Andersson007]

@unnecessary-username thanks for the contribution! We have a lot to do, so would be nice if you continue your contribution here:)

[Andersson007]

See our issue tracker and PRs. We'd be grateful for any ideas / opinions / fixes / etc.

[unnecessary-username]

Thanks @Andersson007 :) I am not an expert in MySQL but I will spend some time to see if anything else I could contribute to.

[Andersson007]

Thanks @Andersson007 :) I am not an expert in MySQL but I will spend some time to see if anything else I could contribute to.

@unnecessary-username frankly speaking, I'm not an expert too:) Ok, thank you!