Configure stale-management rules and cleanup syntax

Description The current stale-management.yml workflow uses the default settings for the actions/stale action.

The Problem

Aggressive Closing: Without configuration, the action will tag and close all issues older than 60 days, including important bugs or pinned issues.

Generic Messages: The default stale message is generic and doesn't guide the user on what to do.

Redundancy: The repo-token input is no longer required for this action version.

Proposed Fix

Add configuration to exempt specific labels (e.g., pinned, security).

Customize the stale/close messages to be more friendly.

Remove the redundant repo-token line.

Fix the indentation of the schedule cron job for better readability.

Open stale-management.yml and review its actions/stale settings and schedule indentation. Configure exemptions for labels such as pinned and security, replace the stale and close messages, remove the redundant repo-token input, and confirm the workflow syntax remains valid.

Written by the indexing model from the issue text.