fix/remove executable bit

[technophile-04]

Description:

The reason we switched to using github api was #381

Why We Made This Change

The Problem

The GitHub Actions workflow using changesets/action@v1.5.3 was failing with this error:

Error: Unexpected executable file at bin/create-dapp-se2.js, GitHub API only supports non-executable files and directories.

Root Cause

The file bin/create-dapp-se2.js had executable permissions (100755 or -rwxr-xr-x). This is the Unix file mode that allows a file to be run directly like ./create-dapp-se2.js.

When the changesets action tries to create a Pull Request, it uses the GitHub API to commit files. However, the GitHub API has a limitation: it cannot create or update files with the executable bit set.

The Fix

We changed the file mode from 100755 (executable) to 100644 (non-executable):

mode change 100755 => 100644 bin/create-dapp-se2.js

Why This Doesn't Break Anything

You might wonder: "If it's a CLI binary, doesn't it need to be executable?"

The answer is no, for two reasons:

1. npm handles permissions automatically - When someone installs your package via npm install -g create-eth or runs npx create-eth, npm reads the "bin" field in package.json and automatically sets the executable permission on the target system.

2. Node runs it anyway - When you run node bin/create-dapp-se2.js or yarn cli, Node.js interprets the file directly. The executable bit is only needed if you want to run it as ./bin/create-dapp-se2.js without the node prefix.

Summary

Before	After
File mode 100755 (executable)	File mode 100644 (non-executable)
GitHub API rejects it	GitHub API accepts it
Changesets action fails	Changesets action works
CLI still works ✓	CLI still works ✓

Merging this and trying once