Consider globally renaming `fnr` to `findr`

[theNerd247]

The name of the library is findr and I've noticed as I browse through the code asking myself: "what's fnr?". I am now realizing that this may just be a shorthand for findr? If this is a case I would like to suggest replacing fnr occurrences in code and documentation with findr and may even go as far as renaming the packages themselves.

Consider the following two import statements:

1. current import

   import { fnr } from "@findr/text"

2. with fnr changed

   import { findr } from "@findr/text"

I would say (2) above is more readable as fnr feels like a typo. Further, I would say that if one sees the function findr in their (potentially large) codebase they would immediately know what it is and which package it's associated with where as fnr requires an extra step for the developer's brain.

From a personal perspective I'm finding myself typing findr-text instead of fnr-text when running package commands

[theNerd247]

Green light on changing the package names

[theNerd247]

depends on #5 being resolved first.