Resolving next-pylint issues for azure-ai-ml sdk

[ZubaeyrMSFT]

Description

Resolving next-pylint issues for azure-ai-ml SDK.
ISSUE #43635 : azure-ai-ml needs linting updates for pylint version 3.3.6

These are the pylint issues that I had to fix. Each of my changes fall in some of the below categories:

do-not-log-exceptions-if-not-debug: Do not log exceptions in levels other than debug, it can otherwise reveal sensitive information.
do-not-log-raised-errors: Do not log an exception that you re-raise as is
try-except-raise: The except handler raises immediately (basically doing nothing in catch statement and reraising the error)

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[Copilot]

Pull Request Overview

This PR resolves pylint issues in the azure-ai-ml SDK by improving code style and simplifying error handling. The changes focus on import statement ordering, adjusting log levels, and removing redundant try-except blocks.

Key Changes:

• Alphabetized import statements to follow PEP 8 conventions
• Changed log levels from warning/error to debug in exception handlers
• Simplified error handling by removing try-except blocks in create_or_update, archive, and restore methods