fix: add translate callback support

Motivation and Context

callbacks can use a runtime expression as their path value, when we translate the path in http-spec we sanitize it so, for example, '{$request.body#/newPetAvailableUrl}' & '{$request.body#/returnedPetAvailableUrl}' become {} & {} and are now identical and are given the same identifier which is resulting in issues when attempting to get nodes by id

see issue getting node by id here: #15026

Description

Added a new context, callback, to identify when a callback is being translated. If it is a callback, do not sanitize the path. Added tests to cover generateIds for httpOperation and httpCallbackOperation Added a test for callback translation

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] This PR's code follows as closely as possible the coding style/guidelines of this project.
[ ] I have added error reporting and followed the error reporting guidelines.
[ ] I have added event tracking and followed the event tracking guidelines.
[ ] I have updated any relevant documentation accordingly to reflect this PR's changes.
[ ] I have added automated tests (unit/integration/e2e/other) to cover my changes.
[ ] All new and existing tests pass locally (excluding flaky CI tests).

stoplightio / http-spec