I noticed that in the 75-Blind-Questions/README.md there are a columns for Java and JS solutions, add them to the Beginner level/README.md and Intermediate level/README.md

Hi everyone,

After reviewing the current structure of our repository, I suggest we restructure it to improve organization and make it easier for contributors and users to navigate.

The proposed structure is as follows:

You can access this diagram here

- solutions
  - [language]
    - [problem-id]
- levels
  - [level-name]
 

Benefits of this structure:

1. Solutions are grouped by language: By creating subdirectories for each programming language, we can easily find and compare solutions in a particular language.

2. Solutions are grouped by problem ID: By naming each solution file with the corresponding problem ID, we can easily find the solution for a specific problem.

3. Levels are grouped together: By creating a separate directory for each level, we can easily find the problems of a certain difficulty.

Here's an example of what the new structure would look like with some sample data:

- solutions
  - c++
    - 0001.cpp
    - 0002.cpp
  - javascript
    - 0001.js
    - 0002.js
  - python
    - 0001.py
    - 0002.py
    
- levels
  - beginner
    - README.md
  - intermediate
    - README.md

Implementation steps:

1. Create the "solutions" and "levels" directories at the root of the repository.

2. Move the current solution files into the appropriate subdirectories based on their programming language and problem ID.

3. Move the current problem files into the appropriate level directories.

4. Update the README file to reflect the new structure and provide instructions for contributors on how to add new solutions or problems.

5. Update any links or references to files in the repository to reflect the new structure.

Rules to keep this structure clean:

1. Add new solutions to appropriate language and problem ID directory under "solutions" directory.

2. Add new problems to appropriate level directory under "levels" directory.

3. Use consistent naming convention for file names, no capital letters and problem id is four digits.

Since the number of leetcode problems is about 2000+

4. Update README file whenever changes made to repository structure or new problems added.

5. Use relative links in the repository to refer to files in other directories.

Let me know if you have any questions or concerns about this proposed change. Thanks!

Could you please assign me to fix this file? I believe it contains many unnecessary spaces that need to be removed, and I've also noticed that some problems are currently not linked.