Int 11348 stop getting machine details

[Gonzalo-Avalos-Ribas]

Description

Thank you for contributing to a JupiterOne integration!

Please include a summary of the change and which issue is fixed. Please also
include relevant motivation and context. List any dependencies that are required
for this change.

Summary

Machine details endpoint should not be called since it returns the same data as the list machines endpoints. In this integration there is a hard cap of 3000 requests per hour. We should not do unnecessary requests.

We should check if its neccesary to have the user_endpoint entity to begin with. Moving forward, we'd like to have types that are specific to a integration, and also that have different data.

For now, don't remove the user_endpoint entity since it might be used for costumer queries.

Type of change

Please leave any irrelevant options unchecked.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to
  not work as expected)
• This change requires a documentation update

Checklist

General Development Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Integration Development Checklist:

Please leave any irrelevant options unchecked.

• I have checked for additional permissions required to call any new API
  endpoints, and have documented any additional permissions in
  jupiterone.md, where necessary.
• My changes properly paginate the target service provider's API
• My changes properly handle rate limiting of the target service provider's
  API
• My new integration step is instrumented to execute in the correct order
  using dependsOn
• I have referred to the
  JupiterOne data model
  to ensure that any new entities/relationships, and relevant properties,
  match the recommended model for this class of data
• I have updated the CHANGELOG.md file to describe my changes
• When changes include modifications to existing graph data ingestion, I've
  reviewed all existing managed questions referencing the entities,
  relationships, and their property names, to ensure those questions still
  function with my changes.

[Gonzalo-Avalos-Ribas]

They even used the same type, endpoint had 'name' and Odatainformation as additional. The name was also on the machine response 🐛

[gastonyelmini]

LGTM!

[j1-internal-automation]

🚀 PR was released in v1.8.0 🚀