chore(main): release 1.2.0 (#29)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

chore(main): release 1.1.0 (#22)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

fix(release): unblock publishing of tagged releases (#21)

Two independent defects kept the Release workflow from ever publishing
1.0.0.

release-please derived a component from the "@fx/tx" package name and
tagged the release "tx-v1.0.0", but the workflow asserts a plain
"v${version}" tag in three places. The assertion failed and the job
aborted before the publish step. Setting include-component-in-tag to
false keeps the tag as "v1.0.0" and matches what the workflow expects.

npm then parsed "package/fx-tx-1.0.0.tgz" as a GitHub owner/repo
shorthand rather than a file path, and tried to resolve it over SSH:

  git --no-replace-objects ls-remote \
    ssh://git@github.com/package/fx-tx-1.0.0.tgz.git

Prefixing the path with "./" makes npm-package-arg classify it as a
file spec so the tarball is published.