Add debug config for tiled register

[Wiebke]

This PR adds a VS Code configuration for debugging the tiled register process. It requires an already running Tiled server instance and the parameters specified within the input prompts need to match the configuration from that running process.
The added launch configuration is equivalent to the script under tiled/tiled_catalog_register.sh

The reasons for not retrieving these parameters from environment variables (as in the script linked above) are explained in #10. In short, environment variables are resolved only after the launch configuration is assembled and can thus not be used within the command.

This PR also resolves #10, and includes an update to the tiled serve debug configuration.

[rajasriramoju]

The debug configuration for tiled_catalog_register works great!

I had some feedback with testing it. When entering the input variables for Tiled API Key, and path to raw data, since there aren't default values, I made a mistake of assuming that default values would be picked from the .env file. Which isn't a right assumption since the issue you are trying to solve is that these variables are not picked from the .env file. I wonder if this will be an assumption made by others unfamiliar with the reason why this debug config exists.

Another minor point. When entering the value for these variables, I tried two things: entering the string as is, or with quotation marks as we do in the .env file. So, for example, if an environment variable is:
API_KEY="abc"
I tried entering just abc and "abc" in case the two would yield a different result. The first case works correctly. The second option yields an error like this. Would we need to mention the right way to enter these values or is that something people would be familiar with?

[rajasriramoju]

For testing these debug configurations, I set breakpoints in the adapter read functions and tested it that way.

For tiled_config_serve, with a breakpoint set on the gb file read adapter function, if I open a gb file, it hits the breakpoint correctly. Which is perfect so far. If I go back to the list view of files, and open the same file immediately, the breakpoint doesn't get triggered. I wonder if this is a thing with our adapter or tiled; maybe if the same file is opened consecutively, it's not read twice but maybe some history is retained. But this is something I wanted to bring to attention if it's not a known thing.

[Wiebke]

Thanks for looking at this and testing. I updated the input descriptions to instruct users to copy values from .env without quotes.