Fix issue #36271 to disambiguate json string
pd.read_json() fails currently for strings that look like fsspec_url and contain "://". adding another condition to fix this at least in most cases

- [X] closes #36271
- [ ] tests added / passed
- [ ] passes `black pandas`
- [ ] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [ ] whatsnew entry

Hello @tbachlechner! Thanks for updating this PR. We checked the lines you've touched for [PEP 8](https://www.python.org/dev/peps/pep-0008) issues, and found:





There are currently no PEP 8 issues detected in this Pull Request. Cheers! :beers: 

##### Comment last updated at 2020-11-11 15:02:53 UTC Does this close an issue? Can you add a test? @jreback yes, this ought to be caught, pd.read_json() is claimed to accept a json string, but it fails for any json string containing `://`- which is a lot of json strings. For now we pinned the version pandas==1.0.5. I'm busy shipping products, but I'll see if I get to a fix at some point. The underlying issue though is that `is_fsspec_url()` should not be returning `True` when it is not a URL, removing json is just a hack that probably does not fix other problems that likely exist. I agree that `is_fsspec_url()` should be better, and clearly is failing for this JSON case. 
Does the regex I suggested earlier ( `"^\s*[\[{]"` ) not suffice? mypy complaint This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. are there opinions about moving `read_json(json_string)` into a function like `parse_json(json_string)` for an API-breaking 1.2+ release (are there more `read_` functions that would need `read_` vs `parse_`)? Something like:
```py
def parse_json(json:str, **kwargs) -> DataFrame:
    buffer = StringIO(json)
    data = read_json(buffer, **kwargs)
    buffer.close()
    return data
```
and a deprecation warning for 1.2 when passing a json string to `read_json`.

edit:
`read_excel`  has the same 'issue', it accepts bytes. > are there opinions about moving read_json(json_string) into a function like parse_json(json_string)

IIRC there was a discussion at some point of making a `read_jsons` mirroring the stdlib's `json.load` vs `json.loads` (or maybe the discussion was about pickle?) it wouldn't be unreasonable to deprecate passing a str (that is not a path) to read_josh and instead only accept a StringIO

i don't think this is much of any issue for pickle as it needs bytes and so str always means a file

excel i think is the same

only read_josh accepts str as an actual transmission format (read_csv as well of course is similar but i think we are restrictive there already) closing as stale. if you would like to continue, pls ping.