This is information you need to get from your hosting provider. If they have some kind of control panel to manage your account, the information might be in there. Otherwise, contact their customer service and ask.
No. You should leave the error mode set to exceptions.
It is, but you shouldn’t have code that unconditionally displays the raw database errors.
You should only catch and handle database exceptions in your code for user recoverable errors, such as when inserting/updating duplicate or out of range data, where you would test the error number in the exception handling and setup a helpful message for the user letting them know what was wrong with the data that they submitted. For all other error numbers, just re-throw the exception and let php handle it. For all other cases, do nothing in your code and let php catch and handle the database exceptions, where php will display or log the actual error information, the same as php errors. On a live/public server, you would log all php errors, which would now include the raw database errors.
If it were me then I would look for information from the hosting provider, as Kicken said. I would do that before uploading my website. They probably have some samples. I would try to interact with a database in a simple site, just to learn how things work. Probably what you have already uploaded can be left and used when you are ready to but if possible it would probably help to create something simple to learn from.