Reorganize the User’s manual

[ziotom78]

This PR addresses issue #341.

• Use PyData as the default theme for docs and update Sphinx and deps
• Rework the structure of the documentation
• Check that the documentation is consistent and reads seamlessly

[ziotom78]

I have completed fixing the grammar. Could somebody please have a look at the way the documentation looks now? Here is a screenshot with the new style:

[paganol]

Hi @ziotom78, I like it, thanks!! I just added an example for the high level interface in the noise section.

I also took the opportunity for changing the default behavior of Simulation.add_noise, before we had to pass explicitly the random number generator, now, if random is empty, self.random is used. This change doesn't really belong to this PR, so if you think that it should be in a separate PR I can do that, let me know.

litebird_sim/litebird_sim/simulations.py

Lines 1549 to 1574 in bcf9cc0

	def add_noise(
	self,
	random: Union[np.random.Generator, None] = None,
	noise_type: str = "one_over_f",
	component: str = "tod",
	append_to_report: bool = True,
	):
	"""Adds noise to tods.
	This method must be called after having set the instrument,
	the list of detectors to simulate through calls to
	:meth:`.set_instrument` and :meth:`.add_detector`.
	The parameter `random` must be specified and must be a random number
	generator thatimplements the ``normal`` method. You should typically
	use the `random` field of a :class:`.Simulation` object for this.
	"""
	if random is None:
	random = self.random
	add_noise_to_observations(
	observations=self.observations,
	noise_type=noise_type,
	random=random,
	component=component,
	)

[ziotom78]

I also took the opportunity for changing the default behavior of Simulation.add_noise, before we had to pass explicitly the random number generator, now, if random is empty, self.random is used. This change doesn't really belong to this PR, so if you think that it should be in a separate PR I can do that, let me know.

I know it’s boring, but having a separate PR for it would be clearer to users. This would let us properly advertise this change in the CHANGELOG by referencing the right PR.

[paganol]

For me we can merge