HDDS-5966. [HTTPFSGW] Update module doc, and place it in Ozone project docs

[dombizita]

What changes were proposed in this pull request?

Added proper documentation for the HttpFS gateway.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-5966

How was this patch tested?

Not really needed, CI on my fork: https://github.com/dombizita/ozone/actions/runs/4105032540

[umamaheswararao]

@DaveTeng0 @swamirishi

[DaveTeng0]

looks good to me~

[fapifta]

Hi @dombizita thank you for working on the documentation piece for HttpFS, I have added some comments around wording. Probably I am not 100% right, it would be nice to get a native speaker to review as well though. :)

[fapifta]

For the following tables I would like to suggest to use the following terms:

• supported
• not implemented in Ozone
• not implemented in Ozone FileSystem API

For this to be meaningful, we should add the note about the internals I have suggested earlier.

[dombizita]

we should add the note about the internals I have suggested earlier.

I'm not sure I got this part, what note do you think of?

[dombizita]

thanks for the review @fapifta, I addressed them, I had only one question regarding your last comment.

[smengcl]

Suggested change

	Ozone HttpFS is forked from the HDFS HttpFS endpoint implementation ([HDDS-5448](https://issues.apache.org/jira/browse/HDDS-5448)). It is added as a separate role to Ozone, like S3G.
	Ozone HttpFS is forked from the HDFS HttpFS endpoint implementation ([HDDS-5448](https://issues.apache.org/jira/browse/HDDS-5448)). Ozone HttpFS is intended to be added optionally as a role in an Ozone cluster, similar to [S3 Gateway]({{< ref "design/s3gateway.md" >}}).

[fapifta]

Thank you @dombizita to address the comments, I have restarted the failed CI check, let's see, +1 to commit once it gets green ;)