Fix boolean condition in publish.yaml

[mosuem]

As seen in https://github.com/dart-lang/native/actions/runs/6075163490/job/16511857492?pr=120, the publish.yaml seems to incorrectly retrieve the boolean value.

Fix it by using the JSON trick from health.yaml, tested using publish_internal.yaml.

CC @dcharkes

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[github-actions]

PR Health

Package publish validation ✔️

Details

Package	Version	Status
package:dart_flutter_team_lints	1.0.0	already published at pub.dev
package:firehose	0.3.27	already published at pub.dev

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

License Headers ✔️

Details

// Copyright (c) 2023, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

Files
no missing headers

All source files should start with a license header.

Changelog Entry ✔️

Details

Package	Changed Files

Changes to files need to be accounted for in their respective changelogs.

Coverage ✔️

Details

File	Coverage

This check for test coverage is informational (issues shown here will not fail the PR).

[devoncarew]

lgtm

[HosseinYousefi]

Why is this necessary if env is always false?

[HosseinYousefi]

Ah nevermind, the publish internal is for testing the trick.

I've seen the first commit test. Weird that the && doesn't work!