Nightly requirement parsing for different cases.

When I was trying to add more nightly dependencies of beamlime, I ran into these cases:

• Package name is not same as repository name. (for ess-dmsc/ess-streaming-data-types)
• Default branch is master not main. (for Textualize/rich)

Both of the dependencies I mentioned don't really have to be nightly dependencies,
since ess-streaming-data-types is not actively updated at the moment,
and Textualize/rich is relatively mature package, so breaking changes are not expected.

But I am reporting this issue since these cases might come again later,
for example, ess-steraming-data-types (from https://github.com/ess-dmsc/python-streaming-data-types) might be actively maintained later,
then we will want to add them into the nightly dependencies.

So if we run into these cases again, maybe we can update the copier answers format and make_base.py to support these cases.

Start by reading the copier answers format and make_base.py to trace how nightly dependencies are parsed and repository metadata is selected. Reproduce the cases for ess-dmsc/ess-streaming-data-types and Textualize/rich, then verify that package names differing from repository names and repositories using master instead of main can be represented and generated correctly.