DAOS-18881 object: increment counters on csum errors

[janekmi]

Restored after #17828

Steps for the author:

• Commit message follows the guidelines.
• Appropriate Features or Test-tag pragmas were used.
• Appropriate Functional Test Stages were run.
• At least two positive code reviews including at least one code owner from each category referenced in the PR.
• Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

• Gatekeeper requested (daos-gatekeeper added as a reviewer).

[github-actions]

Ticket title is 'checksum/csum_error_logging.py:CsumErrorLog.test_csum_error_logging - failed due to Checksum Error Log not incremented'
Status is 'In Progress'
Labels: 'ci_master_daily,scrubbed_2.8,triaged'
https://daosio.atlassian.net/browse/DAOS-18881

[NiuYawei]

I don't think we should regard all csum errors as media error.

What about introducing a parameter to this function? Like
obj_log_csum_err(daos_unit_oid_t oid, bool media_err)
{
Raise general csum error event;
if (media_err) {
Raise media csum error event;
}

This function is called in three places, one is from client csum error reporting, the other two have network transfer involved, so they are not media error, however, there is a fault injection of DAOS_CSUM_CORRUPT_DISK for simulating media error, so the "obj_log_csum_error(oid, true)" should only be called for this fault injection case. What do you think?