Add extra integration tests for Resource lock

[psnoch-akamai]

✔️ How to Test

make TEST_ARGS="-run TestTryToLockTwoResourcesWithTheSameType"
make TEST_ARGS="-run TestTryToCreateWithInvalidData"

[Copilot]

Pull request overview

This PR adds two new integration tests for the Resource lock functionality to improve test coverage. The tests verify error handling for edge cases: attempting to create multiple locks of different types on the same resource, and attempting to create a lock with an invalid entity ID.

Key Changes

• Added TestTryToLockTwoResourcesWithTheSameType to verify that conflicting lock types cannot be applied simultaneously to the same resource
• Added TestTryToCreateWithInvalidData to verify proper error handling when creating locks with non-existent entity IDs
• Created supporting test fixtures with recorded HTTP interactions for both test scenarios

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 1 comment.

File	Description
test/integration/locks_test.go	Added two new test functions with error validation for lock creation edge cases
test/integration/fixtures/TestLockTryToLockResourceTwice.yaml	HTTP interaction recording for the duplicate lock type test scenario
test/integration/fixtures/TestLockTryToCreateWithNotExistingEntityID.yaml	HTTP interaction recording for the invalid entity ID test scenario

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The variable name errAlreadyExist is misleading. The test verifies that conflicting lock types cannot coexist, not that a duplicate lock already exists. Consider renaming to errConflictingLock or err to better reflect the actual validation being performed.

Suggested change

	_, errAlreadyExist := client.CreateLock(context.Background(), createOpts)
	require.Error(t, errAlreadyExist)
	_, errConflictingLock := client.CreateLock(context.Background(), createOpts)
	require.Error(t, errConflictingLock)