Log and data cleanup

[harp-intel]

This pull request primarily focuses on improving logging verbosity and minor data handling in the flame graph rendering and script support checks. The most notable changes include reducing log levels for unsupported features to avoid cluttering logs, and making a small fix to whitespace handling when extracting maximum depth information.

Logging improvements:

• Changed several log statements from Info to Debug level in internal/common/targets.go to reduce noise when scripts or tables are not supported for a given target, architecture, vendor, or microarchitecture. [1] [2] [3] [4]

Data handling fix:

• Trimmed whitespace from the "maximum depth" section in maxRenderDepthFromOutput to ensure consistent output.
• Removed redundant whitespace trimming in renderFlameGraph since the value is now already trimmed, preventing double processing.

[Copilot]

Pull request overview

This pull request reduces logging noise and improves data consistency in the flame graph rendering pipeline. The main focus is making unsupported feature checks less verbose while ensuring whitespace is handled consistently.

Key Changes:

• Reduced log verbosity for unsupported scripts and tables from Info to Debug level to prevent cluttering logs with expected conditions
• Consolidated whitespace trimming for maximum depth value to a single location to avoid redundant processing

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
internal/common/targets.go	Changed three log statements from Info to Debug when scripts are not supported for specific architectures, vendors, or microarchitectures
internal/common/common.go	Changed log statement from Info to Debug when a table is not supported for a target
cmd/flame/flame_tables.go	Added whitespace trimming when extracting maximum depth from script output
cmd/flame/render_html_flamegraph.go	Removed redundant whitespace trimming now that the value is pre-trimmed upstream