Rename/rebrand project and artifacts to LeafContourEFD

[maple60]

Motivation

• Rebrand the project from “Leaf Shape Analysis Tool” / leaf-shape-tool to LeafContourEFD to reflect the new product name and update distribution artifacts, documentation, and entry points.
• Ensure build, packaging, and release workflows produce artifacts and release notes that use the new name consistently across platforms and docs.

Description

• Updated package metadata and entry points by renaming the project in pyproject.toml (name = "leaf-contour-efd") and changing the console script to leaf-contour-efd.
• Adjusted PyInstaller spec and build outputs by setting the produced executable/collection names to LeafContourEFD in build.spec and updated references to the dist/LeafContourEFD/ folder.
• Updated CI/release workflow /.github/workflows/release-standalone.yml to produce and upload artifacts named LeafContourEFD-*.zip|tar.gz and to inspect executables named LeafContourEFD(.exe) when generating release notes.
• Renamed documentation, website config, README (English/Japanese), setup scripts (setup_unix.sh, setup_windows.bat), and in-source strings (docstrings and window title) to LeafContourEFD, and updated repo/Docs URLs and references accordingly; also updated uv.lock package name.

Testing

• No automated test runs were executed as part of this change; only source, docs, and CI/workflow configuration were modified.
• The GitHub Actions release workflow (release-standalone.yml) was updated to use the new artifact names and will run PyInstaller and artifact upload when triggered by CI (build/release runs have not been observed in this PR).

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1c7b96b69d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Regenerate published docs after renaming website content

website/_quarto.yml publishes the site from ../docs, but this change only updates website/*.qmd text and does not regenerate the checked-in docs/ output, so GitHub Pages will still serve old branding/commands (for example docs/index.html still shows LeafShapeTool and old repo links). This leaves user-facing installation instructions inconsistent with the renamed CLI and artifacts until someone runs quarto render and commits the updated docs/* files.

Useful? React with 👍 / 👎.

[maple60]

@codex, thank you.

After renaming, I will manually regenerate the docs by rendering website/.
Are there any issues?