fix: commit linter running on generated messages

[FrankFlitton]

TL;DR

Commit linter was running on auto-generated content with long URLs to github artifacts, triggering the lines longer than 100 chars rule.

Type

• Bug Fix
• Feature
• Plugin

Are all requirements met?

• Code completed
• Smoke tested
• Unit tests added
• Code documentation added
• Any pending items have an associated Issue

Complete description

• Made sure CI env variable was set - same as linter stage - that it was bypassing.
• Added [skip ci] rule to the generated commit message which is recommended by semantic-release if running within a CI so you can avoid duplicate builds from change log diffs.
• Remote pipeline is incrementally more in common with local dev environment.

Follow-up issue

NA

[codecov]

Codecov Report

Merging #810 (6323177) into master (58d5d1a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #810   +/-   ##
=======================================
  Coverage   63.37%   63.37%           
=======================================
  Files         527      527           
  Lines       13362    13362           
  Branches     2540     2540           
=======================================
  Hits         8468     8468           
  Misses       4894     4894           

[flyte-bot]

🎉 This PR is included in version 1.9.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀