Replace all instances of BoM or Bom in class names with BOM

[Andy-Grigg]

This PR changes all instances of 'Bom' or 'BoM' in class names with 'BOM'.

This change is to ensure we are as compliant with PEP8 as is reasonable. Some considerations:

• The Granta-preferred capitalization for the acronym is 'BoM'. PEP8 states that class names should use CapWords here, and that when using CapWords acronyms should be fully capitalized. Therefore, Bom1711..., BomImpactedSubstances..., etc. change to BOM1711..., BOMImpactedSubstances..., etc.
• All references to these classes in docstrings and RST files have been changed
• Any references to BoMs in method, module, and package names are unchanged, since they already were (and remain) fully lowercase
• References to BoMs in docstrings (when not referring to a class) remain as 'BoM'
• Classes in the imported ansys-grantami-bomanalytics-openapi package capitalize the 'B' only, this is due to the way the code generator template generates Python class names and cannot be changed without a great deal of effort

I did make a few changes to private docstrings, but these were just to standardize on 'BoM' when referring to the concept of a Bill of Materials, as opposed to 'bom'.

[da1910]

One missing BOM, otherwise looks to do what it says on the tin.

I'm mostly 👎 to the change in general, but I do understand the logic following PEP-8

[da1910]

Missed a BOM here

[Andy-Grigg]

One missing BOM, otherwise looks to do what it says on the tin.

I'm mostly 👎 to the change in general, but I do understand the logic following PEP-8

I was trying to figure out when making this change if it's more or less readable than it was originally. I was also negative when making the change, but I put that down to my bias in having grown accustomed to the original class.

I suppose the debate is whether 'BoM' is really an acronym in the same way that 'HTTP' is (the example used in PEP8). I know BoM is an acronym, but it's vocalized as 'bomb', and so you're more likely to expect to see it as a regularly-cased CapWord string.

[Andy-Grigg]

I'm erring on the side of rejecting this PR. My reasoning is as follows:

• Whilst PEP8 states that an acronym should be all-caps in class names, the cited example in PEP8 (HTTP) is an initialism, not an acronym
• I believe the intent behind PEP8's stance is that if you have a class name based on an initialism, i.e. you say each letter separately (HTTP), then it should be capitalized.
• This isn't the case for BoM/BOM, even though it's all caps it's pronounced as a word.

The current code is largely consistent with this. The one exception is in places where we refer to Granta-specific concepts such as 17/11 XML BoM formats, where we use the Granta capitalization of BoM.

As a result, I'll close this PR and delete the branch. I'll create an Issue that refers to it, copy this conclusion there, and close it.