Ensure deprecation notices come out in the docs

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

This merge request updates documentation and code to improve clarity around deprecated features in a GitLab Terraform provider. The main changes include:

Documentation improvements:

• Enhanced deprecation messages to be more specific about when features will be removed (version 19.0)
• Clarified that authentication tokens are only available during resource creation, not when reading data, and will always appear blank in data sources
• Added clearer guidance on which newer resources to use instead of deprecated ones

Deprecated resource notifications:

• Added deprecation warnings to several integration resources (Custom Issue Tracker, Harbor, Jenkins, Redmine, Telegram) directing users to newer alternatives
• Marked the gitlab_runner resource as deprecated in favor of gitlab_user_runner
• Added deprecation notices to the gitlab_label resource, recommending gitlab_project_label instead

Parameter updates:

• Updated various deprecated parameters to specify they'll be removed in version 19.0 and suggest modern alternatives
• Improved messaging around project identification parameters, recommending the use of project instead of older project_id or full_path parameters

These changes help users understand which features are being phased out and provide clear migration paths to newer, supported alternatives.