removing the call to 'publish' the internal dev specification using a production publish command

[eddalmond1]

Description

proxygen spec publish build/specification/internal-dev/eligibility-signposting-api.yaml --no-confirm will publish the internal-dev specification to the production catalogue. We don't want to do this. There are only 2 environments for the specification - 'ptl / preprod / uat ' and prod. These are covered by other actions.

Context

Stops publishing of dev specification to prod!

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[TOEL2]

I understand your point about this not being needed for dev, that was my oversight - but we have many green pipeline runs of this working, does that mean something changed?