I'm not totally certain what happened, but I think you got something like a nonbreaking space between "find" and ".". Nonbreaking spaces are unicode characters that look just like normal spaces, but are intended not to indicate valid places to wrap a line of text. But while they look like normal spaces, the shell has no idea what to do with them, and just treats them like normal characters. One consequence of this is that it doesn't recognize them as delimiters between a command and its argument. Here's an example:
$ find . -name ‘*.blade.php’ -not -path ‘*/vendor/*’ | wc -l # With normal space
$ find . -name ‘*.blade.php’ -not -path ‘*/vendor/*’ | wc -l # With nonbreaking space
-bash: find .: command not found
$ find . -name ‘*.blade.php’ -not -path ‘*/vendor/*’ | wc -l # With ALL nonbreaking spaces
-bash: wc -l: command not found
-bash: find . -name ‘*.blade.php’ -not -path ‘*/vendor/*’ : No such file or directory
(Note that I don't have any files that match the pattern, so the count comes out 0.) What's happening in the second command is that I have a nonbreaking space (typed as Option-Space on my Mac) between "find" and ".", so the shell treats "find<nonbreakingspace>." as the command... which isn't recognized. In the third command, I replaced ALL spaces with nonbreaking ones; it recognized the "|" as a delimiter between commands, but things literally everything else on the line is part of a command name.
That error message that the command "find ." wasn't found is the giveaway about what's happening; it's treating the space-like-thing and "." as part of the command, so they show up in the error message that way.
On thing confuses me, though: I'm not sure how you got the nonbreaking space there in the first place. Copy-and-paste to & from Notes shouldn't do any conversion. Maybe you bumped Option by mistake? I dunno.
BTW, I noticed another thing while editing this: the single-quotes you have are fancy (curly) unicode ones that look like perfectly good quotes, but like nonbreaking spaces, are not recognized that way by the shell. This one I do know the source of: in many contexts, macOS will auto-"correct" plain quotes to the fancy type (a feature called "smart quotes"). This tends to wreak havoc with scripts. I'll throw in a recommendation for BBEdit as a good editor that doesn't mess with what you enter, making it good for scripting. It's not free, but even if you don't pay it runs in a limited mode that's still much better for scripting than the builtin editors.