Warn for bytes/str parsing methods

[nanjekyejoannah]

More thinking got me to think maybe we dont need to separate the objects.
@ltratt you are right, "" in py2.x is very close to "" in py3.x: I concluded from this
querying the difference in methods at least by parsing:

Bytes diff (py2.x bytes && py3.xbytes)
array(['__getslice__', '_formatter_field_name_split', '_formatter_parser',
   	'encode', 'format'], dtype='<U27')

Str diff (py2.x str && py3.xstr)

>>> main_list1
array(['__getslice__', '_formatter_field_name_split', '_formatter_parser',
   	'decode'], dtype='<U27')

When I get to runtime warning we can do with the states for the most part without separation.

This PR replaces the former and will do the warnings in several PRs instead of one huge one.

[ltratt]

Looks like a good start to me!

[ltratt]

12:20:53 test test_sys failed -- Traceback (most recent call last):
12:20:53   File "/ci/Lib/test/test_sys.py", line 741, in test_objecttypes
12:20:53     check('', calcsize(vh + 'lic'))
12:20:53   File "/ci/Lib/test/support/__init__.py", line 1292, in check_sizeof
12:20:53     test.assertEqual(result, size, msg)
12:20:53 AssertionError: wrong size for <type 'str'>: got 49, expected 37

That looks like a test that checks the size of a struct? Seems a bit odd to me, so we could consider disabling it?