Add a robot test to cover the case where mapper doesn't supply client cert

[jarhodes314]

Proposed changes

In #2474 (comment), I discussed a minor bug with the mapper's handling of operations that I found while writing robot tests. After some investigation including manual testing, I couldn't reproduce the bug, and then discovered that the issue was my understanding of the robot test code. I have now added the corrected test, as well as correcting the negative case (as due to the same misunderstanding, there was an entirely redundant assertion).

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s)
• I ran cargo fmt as mentioned in CODING_GUIDELINES
• I used cargo clippy as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
370	0	3	370	100	57m48.397999999s

[reubenmiller]

Approved.