[WIP] Update PennyLane pipeline logging support

[mlxd]

Before submitting

Please complete the following checklist when submitting a PR:

• All new features must include a unit test.
  If you've fixed a bug or added code that should be tested, add a test to the
  test directory!

• All new functions and code must be clearly commented and documented.
  If you do make documentation changes, make sure that the docs build and
  render correctly by running make docs.

• Ensure that the test suite passes, by running make test.

• Add a new entry to the doc/releases/changelog-dev.md file, summarizing the
  change, and including a link back to the PR.

• The PennyLane source code conforms to
  PEP8 standards.
  We check all of our code against Pylint.
  To lint modified files, simply pip install pylint, and then
  run pylint pennylane/path/to/file.py.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

---

Context: This PR expands the logging functionality in PennyLane for both internal and inter-library (e.g. Lightning, Catalyst) use.

Description of the Change: Add support for decorator-defined logging functions, and updates the internal usage of logging with this.

Benefits: Allows more ease-of-use by developers to include logging with new functionality to the library.

Possible Drawbacks: Does not replace custom-defined log-level messages and trace-level expansion of functions.

Related GitHub Issues: #5528

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit doc/releases/changelog-dev.md with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[mlxd]

[sc-61591]