Remove line regarding moving the catalog into the repository from the README

[AlajeBash]

Fixes

Fixes #3202 by @AetherUnbound

Description

Remove line regarding moving the catalog into the repository from the README.MD file.

Testing Instructions

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[dhruvkb]

@AlajeBash here we see why @obulat mentioned that making PRs from main is not recommended. Now the history of this PR contains all the old commits from your last PR.

Here's how we can fix this.

1. This will reset main to a pristine condition, exactly how it in on WordPress/openverse.

   $ git checkout main
   $ git fetch upstream main
   $ git reset --hard upstream/main

2. Then we create a new branch specifically for the issue we're solving.

   $ git checkout -b 3202_update_readme
   $ <make changes and commit>
   $ git push origin 3202_update_readme

3. Finally we make a PR from your repo's 3202_update_readme to our repo's main branch.

4. Once the PR is merged, you can delete 3202_update_readme in your repo and checkout a new branch for the next issue, by repeating step 1.